[ https://issues.apache.org/jira/browse/AMQ-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mykola Markov updated AMQ-6602: ------------------------------- Attachment: AMQ-6602.patch Can be fixed with AMQ-6602.patch > Memory leak when undeploying webapp with ActiveMQ client > -------------------------------------------------------- > > Key: AMQ-6602 > URL: https://issues.apache.org/jira/browse/AMQ-6602 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client > Affects Versions: 5.14.3 > Reporter: Mykola Markov > Priority: Minor > Labels: leak > Attachments: AMQ-6602.patch > > > I have a web app with an ActiveMQ client. When undeploying the app, Tomcat > logs the following messages. > {code} > 15-Feb-2017 17:53:31.760 WARNING [localhost-startStop-2] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [Engine] appears to have started a thread named [ActiveMQ > Session: ID:comp-41144-1487186920452-1:1:3] but has failed to stop it. This > is very likely to create a memory leak. Stack trace of thread: > java.lang.Object.wait(Native Method) > java.lang.Object.wait(Object.java:502) > > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:119) > > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:42) > 15-Feb-2017 17:53:31.761 WARNING [localhost-startStop-2] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [Engine] appears to have started a thread named [ActiveMQ > Session: ID:comp-41144-1487186920452-1:1:2] but has failed to stop it. This > is very likely to create a memory leak. Stack trace of thread: > java.lang.Object.wait(Native Method) > java.lang.Object.wait(Object.java:502) > > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:119) > > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:42) > 15-Feb-2017 17:53:31.762 WARNING [localhost-startStop-2] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [Engine] appears to have started a thread named [ActiveMQ > Session: ID:comp-41144-1487186920452-1:1:4] but has failed to stop it. This > is very likely to create a memory leak. Stack trace of thread: > java.lang.Object.wait(Native Method) > java.lang.Object.wait(Object.java:502) > > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:119) > > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:42) > 15-Feb-2017 17:53:31.762 WARNING [localhost-startStop-2] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [Engine] appears to have started a thread named [ActiveMQ > Session: ID:comp-41144-1487186920452-1:1:10] but has failed to stop it. This > is very likely to create a memory leak. Stack trace of thread: > java.lang.Object.wait(Native Method) > java.lang.Object.wait(Object.java:502) > > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:119) > > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:42) > 15-Feb-2017 17:53:31.763 WARNING [localhost-startStop-2] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [Engine] appears to have started a thread named [ActiveMQ > Session: ID:comp-41144-1487186920452-1:1:6] but has failed to stop it. This > is very likely to create a memory leak. Stack trace of thread: > java.lang.Object.wait(Native Method) > java.lang.Object.wait(Object.java:502) > > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:119) > > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:42) > Feb 15, 2017 5:53:31 PM org.apache.catalina.core.ApplicationContext log > INFO: Closing Spring root WebApplicationContext > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)