> From: Debbie Shapiro [mailto:dshap...@cardiacscience.com] 
> Subject: RE: Web service not starting up as expected

> 3. Schedule a restart 2 minutes into the future.

Exactly what does your restart procedure consist of?  From the symptoms, it 
could be that the restart mechanism is simply not waiting for Tomcat to 
terminate before kicking off a new one.

> Mar 8, 2012 4:37:04 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 8, 2012 4:37:04 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 8, 2012 4:37:04 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/sree] appears to have started a thread
> named [Thread-5] but has failed to stop it. This is very likely to
> create a memory leak.
> Mar 8, 2012 4:37:04 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/sree] appears to have started a thread
> named [Thread-7] but has failed to stop it. This is very likely to
> create a memory leak.
> Mar 8, 2012 4:37:04 PM org.apache.catalina.loader.WebappClassLoader
> checkThreadLocalMapForLeaks
> SEVERE: The web application [/sree] created a ThreadLocal with key of
> type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1809b1ac])
> and a value of type [inetsoft.util.CurrentException.Infomation] (value
> [inetsoft.util.CurrentException$Infomation@246f9f88]) but failed to
> remove it when the web application was stopped. Threads are going to
> be renewed over time to try and avoid a probable memory leak.

Obviously, your webapp indulges in some rather anti-social behavior; that will 
slow down Tomcat termination, but not prevent it.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to