https://issues.apache.org/bugzilla/show_bug.cgi?id=53381
--- Comment #1 from Konstantin Kolinko <knst.koli...@gmail.com> --- The stacktrace mentions org.apache.catalina.loader.WebappClassLoader.clearReferencesStaticFinal(WebappClassLoader.java:2034) org.apache.catalina.loader.WebappClassLoader.clearReferences(WebappClassLoader.java:1929) org.apache.catalina.loader.WebappClassLoader.stop(WebappClassLoader.java:1833) 1. So it happens during cleanup of static fields on web application shutdown. It is one of those features to remedy memory leaks in stopped applications. This particular cleanup can be turned off in Tomcat 6 by setting the following system property to the value of false (e.g. in conf/catalina.properties file): org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES See http://tomcat.apache.org/tomcat-7.0-doc/config/systemprops.html Maybe this feature does not play well with org.aspectj.weaver.loadtime.ClassPreProcessorAgentAdapter Do you use some form of lazy initialization/loading of classes? 2. Looking at WebappClassLoader.stop() line 1833, closing the JARs happens later than this call to clearReferences(). So it is unclear why JARs appear to be closed. To exclude bug 53225, a question: do you have "JreMemoryLeakPreventionListener" in your server.xml? It should not be an issue in 6.0.x - just confirming. -- 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
