hmm, I gave your war a whirl with 5.7-SNAPSHOT (current trunk) and it worked and undeployed once I added the call to stop the pool before the calls to shutdown the executors in com.foo.MainApplication#stop
Really the correct place for the calls to shutdown is when the spring context is destroyed, so after the call to stop the pool from the destroy-method. In that way they cannot interfere with normal connection close etc. There may be some change on trunk that resolved this issue. Can you do some validation with a 5.7-SNAPSHOT. On 17 July 2012 12:06, liny <[email protected]> wrote: > Hi, gtully: > > Thanks for reply. > The solution that is suggested at > https://issues.apache.org/jira/browse/AMQ-3451?focusedCommentId=13416044&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13416044 > AMQ-3451 can't solve the problem. > I did specify "destroy-method" in my WEB-INF/classes/jms-spring-client.xml > as below: > > > And after stop web application by Tomcat manager, spring did call "stop" of > PooledConnectionFactory as below: > > > And "InactivityMonitor" is still running in the background. > These logs can be found in > http://activemq.2283324.n4.nabble.com/file/n4654084/tomcat_log.TXT > tomcat_log.TXT . > > Really appreciated. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Old-issue-Memory-leak-after-stop-web-application-in-Tomcat-tp4653959p4654084.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
