I upgraded to Tomcat 6.0.24 earlier today and started noticing the following messages on Tomcat shutdown. The deployed web app is the same (not the JR webapp, but my own) and does not generate any of these messages on 6.0.20.
12-Feb-2010 14:23:20 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: A web application registered the JBDC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 12-Feb-2010 14:23:20 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak. 12-Feb-2010 14:23:20 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [ObservationManager] but has failed to stop it. This is very likely to create a memory leak. 12-Feb-2010 14:23:20 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: A web application appears to have started a thread named [jackrabbit-pool-1] but has failed to stop it. This is very likely to create a memory leak. 12-Feb-2010 14:23:20 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: A web application created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.threadlo...@8244f74]) and a value of type [org.apache.jackrabbit.core.query.lucene.PerQueryCache] (value [org.apache.jackrabbit.core.query.lucene.perqueryca...@7dc4cd9]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
