Maybe you are referring to this issue in tomcat: http://issues.apache.org/bugzilla/show_bug.cgi?id=42172
If so then that classloader leak was attributed to how log4j was used by the application.
Best wishes, Paul On Apr 25, 2007, at 11:19 AM, [EMAIL PROTECTED] wrote:
You're correct. But there's been a lot of discussion surrounding this issue in the Tomcat forums. Maybe it's because the ClassLoaders don't get GC'ed correctly, but when Tomcat reloads an app, the class data seems to never get GC'ed. The same issue was found with Jetty, so it seems to be a VM issue.
