DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39975>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39975 Summary: Classloader refence leaks in jasper-runtime when webapp has log4j and commons-logging Product: Tomcat 5 Version: 5.0.17 Platform: All OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When the first JSP renderd (since startup) is from a webapp that contains commons-logging and log4j, classes from the 'jasper.runtime' package create a memory leak. Here's a description in more detail 1) User deploys war with commons-logging + log4j jars (quite common) 2) First page is rendered, causing loading and initialization of classes in the 'jasper.runtime' package. 3) Some of these classes (for instance PageContextImpl) contain static commons-logging 'log' fields. 4) In the scenario described, these fields get intialized to a Log4JLogger instance that is loaded from the webapp classloader. The effective result is that code and data in this webapp will never be unloaded. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
