[Bug 56435] New: OpennSSL version in apache tomcat
https://issues.apache.org/bugzilla/show_bug.cgi?id=56435 Bug ID: 56435 Summary: OpennSSL version in apache tomcat Product: Tomcat 6 Version: 6.0.32 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P2 Component: Connectors Assignee: dev@tomcat.apache.org Reporter: swaminathan.muru...@gmail.com can you help me to understand that is HeartBleed bug is present in the tomcat 6.0.32 server or not. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56436] New: OpennSSL version in apache tomcat
https://issues.apache.org/bugzilla/show_bug.cgi?id=56436 Bug ID: 56436 Summary: OpennSSL version in apache tomcat Product: Tomcat 6 Version: 6.0.32 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P2 Component: Connectors Assignee: dev@tomcat.apache.org Reporter: swaminathan.muru...@gmail.com can you help me to understand that is HeartBleed bug is present in the tomcat 6.0.32 server or not. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56436] OpennSSL version in apache tomcat
https://issues.apache.org/bugzilla/show_bug.cgi?id=56436 Chuck Caldarale changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Chuck Caldarale --- Bugzilla is not a support forum. Post your query on the Tomcat users' mailing list - but only after you've looked at the archives and the Wiki. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56435] OpennSSL version in apache tomcat
https://issues.apache.org/bugzilla/show_bug.cgi?id=56435 Chuck Caldarale changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Chuck Caldarale --- Bugzilla is not a support forum. Post your query on the Tomcat users' mailing list - but only after you've looked at the archives and the Wiki. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56438] New: If jar scan does not find context config or TLD config, log a message
https://issues.apache.org/bugzilla/show_bug.cgi?id=56438 Bug ID: 56438 Summary: If jar scan does not find context config or TLD config, log a message Product: Tomcat 7 Version: 7.0.53 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: Catalina Assignee: dev@tomcat.apache.org Reporter: justincranf...@hotmail.com I went through the same process as many others migrating to Tomcat 7. My simple war application took orders of magnitude longer to load than in Tomcat 3.3, and root cause was new Tomcat 7 / Servlet 3.0 jar scanning to look for context config fragments. This is a very painful process. I had to use FINE log level, parse thousands of Tomcat log messages, and google the various messages. This was a waste of time. All Tomcat 7 needed to do was log a message when the jar scan did not find anything in a jar, and recommend adding that jar to one of the filters in catalina.properties. tomcat.util.scan.DefaultJarScanner.jarsToSkip org.apache.catalina.startup.ContextConfig.jarsToSkip org.apache.catalina.startup.TldConfig.jarsToSkip. As an enhancement, please add a log message recommending adding a jar if scanning does not find anything. I would recommend setting the log level to FINE, and explicitly putting a logging.properties override for that message in logging.properties. Anyone new to Tomcat 7 can fix these messages by either following the recommendation, or commenting out the logging.properties override for the message. This is low hanging fruit. It should be straight forward to add, and would be a huge help for anyone new to Tomcat 7 who are unaware of the performance impact of Servlet 3.0 jar scanning. It could even help Tomcat 7 veterans too, when they add/upgrade/replace existing jar files that unknowingly affect jar scanning performance. Thank you. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56438] If jar scan does not find context config or TLD config, log a message
https://issues.apache.org/bugzilla/show_bug.cgi?id=56438 --- Comment #1 from Justin Cranford --- Correction: I migrated from Tomcat 5.5. I wrote Tomcat 3.3 which was a type-o. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56438] If jar scan does not find context config or TLD config, log a message
https://issues.apache.org/bugzilla/show_bug.cgi?id=56438 --- Comment #2 from Justin Cranford --- I manually added these two overrides in Tomcat 7 logging.properties to make is easy to diagnose and fix slow start performance. Consider adding these to the defaults, or even just add them as commented out. I think they would benefit a wider audience. *** conf/logging.properties *** org.apache.tomcat.util.scan.StandardJarScanner.level = FINE org.apache.catalina.startup.Catalina.level = INFO Regarding catalina.properties, these are the filters I had to add for my specific application. Note that some of them should have been filtered by Tomcat 7 default filters tomcat.util.scan.DefaultJarScanner.jarsToSkip. The first 4 should definitely be fixed in the default filters of Tomcat 7, and the rest you can consider on a case-by-case basis: Various JARs - jdom.jar (Default filter "jdom-*jar" missed this jar name) - commons-discovery*.jar (Missing Apache Commons jar filter) - commons-net*.jar (Missing Apache Commons jar filter) - commons-el*.jar (Missing Apache Commons jar filter) - quartz*.jar - el-ri.jar - kxml2.jar - jsch-*.jar - iText-*.jar - jasperreports-*.jar - httpcore-4.1.jar - protomatter-*.jar - stax-api-*.jar - xpp3_min-*.jar - xstream-*.jar - openspml2-toolkit.jar - vijava*.jar - jt400.jar - jsf-api-*.jar Various JDBC JARs - mysql-connector-*.jar - ojdbc*.jar - jtds*.jar - h2-*.jar - ha-jdbc-*.jar - sqljdbc4.jar - db2jcc4.jar Various Application Clustering JARs - jgroups-*.jar - hazelcast-*.jar -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
