Hi gtully: I made a war with source code to reproduce the problem, please download it from https://docs.google.com/open?id=0B-ZFcczN9qxYZmh5dDdoMFVCUkE My GoogleDoc . The Tomcat version is 6.0.33 or above, but I use Tomcat 7.0.28. Before starting this web app, you need to setup a broker TCP address in WEB-INF\classes\jms-spring-client.xml:
Change foo.com:61616 to your own broker. After web app is started, you can see below main page: http://activemq.2283324.n4.nabble.com/file/n4654028/0.png And live threads are: http://activemq.2283324.n4.nabble.com/file/n4654028/1.png The reproduce steps are: 1. Click [Start getting text msg from topic], it will start listening msg from simpleTopic topic. And some ActiveMQ threads are shown as below: http://activemq.2283324.n4.nabble.com/file/n4654028/2.png 2. You can go to ActiveMQ web console to send fake msg into simpleTopic. (optional) Like below: http://activemq.2283324.n4.nabble.com/file/n4654028/3.png 3. Click [Stop getting text msg from topic] will do below methods (in stop() of \WEB-INF\classes\com\foo\MainApplication.java): 4. Go to Tomcat manager to stop this web app. Tomcat will show some logs like below: After web app is stopped, these 4 ActiveMQ threads are still running: http://activemq.2283324.n4.nabble.com/file/n4654028/4.png Hope these can help analysis. Let me know if any! Thank you very much. -- View this message in context: http://activemq.2283324.n4.nabble.com/Old-issue-Memory-leak-after-stop-web-application-in-Tomcat-tp4653959p4654028.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
