On 09/03/2012 18:09, Debbie Shapiro wrote: > Mar 7, 2012 11:30:06 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/sree] appears to have started a thread named > [AWT-Windows] but has failed to stop it. This is very likely to create a > memory leak. > Mar 7, 2012 11:30:06 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/sree] appears to have started a thread named > [Thread-3] but has failed to stop it. This is very likely to create a memory > leak. > Mar 7, 2012 11:30:06 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/sree] appears to have started a thread named > [Thread-8] but has failed to stop it. This is very likely to create a memory > leak.
NB The message above is a SEVERE error, and not a WARNING as the developers you quote have stated. One possible side effect of leaving threads running is that a Tomcat instance might not completely shutdown even having completed it's own internal stop processes, because the JVM is waiting for those threads to complete their work (if they are not daemon threads). p -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
