-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris,
On 11/24/2010 9:47 AM, Pid wrote: > SEVERE: A web application appears to have started a thread named > [MultiThreadedHttpConnectionManager cleanup] but has failed to stop it. > This is very likely to create a memory leak. > > MultiThreadedHttpConnectionManager is a class from HTTP Client. If you are using Axis and it's creating a MultiThreadedHttpConnectionManager, it should be stopping it when the webapp undeploys. So, the question is: are you properly shutting-down the Axis services when your webapp shuts down? If you are, then this is a bug in Axis that should be reported to them. If you aren't, then you need to do so. If you want a quick solution, you can always write your own ServletContextListener and call MultiThreadedHttpConnectionManager.shutdownAll() -- it's a static method that looks like it'll kill all threads from all MultiThreadedHttpConnectionManager objects. Seems like a reasonable hack, as long as commons-http-client was loaded by the WebappClassLoader. ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzxDgkACgkQ9CaO5/Lv0PAYagCgjN6tvR47NshlNwSojGO7LOp2 3eAAnisYOvsvoZBL8R34+azn+K3ZTpoi =RAzC -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
