Hi Mark, Thanks for your response. Doesn't tomcat stop take care of shutting down all the threads? Do we need to handle explicity this case? Thanks Ambica.
-----Original Message----- From: Mark Thomas [mailto:ma...@apache.org] Sent: Friday, May 20, 2016 9:34 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: Re: memory leak in Tomcat 8.0.9 First of all, the subject is wrong. There is no memory leak in Tomcat. There is a memory leak in the application you are running on Tomcat. On 20/05/2016 14:21, Sanka, Ambica wrote: > 2016-05-19 14:03:31,161 [localhost-startStop-2] WARN > org.apache.catalina.loader.WebappClassLoader- The web application > [/fmDirectoryService] appears to have started a thread named [Thread-6] but > has failed to stop it. This is very likely to create a memory leak. Stack > trace of thread: > > java.lang.Thread.sleep(Native Method) > > net.atpco.cluster.support.BaseLocator$AdminTask.run(BaseLocator.java:1 > 41) What isn't clear in the message above? Based on the Java package name and your e-mail address net.atpco.cluster.support.BaseLocator is code that you control. BaseLocator starts a thread so it needs to stop that thread when the web application shuts down. ServletContextListener.contextDestroyed() is usually where such clean-up is performed. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
