About a month ago, I started using ActiveMQ (v5.8.0) that is bundled with TomEE (v1.6.0), and i noticed that in the log too, when I stopped TomEE (to deploy new version of WAR file).
so, I searched google, and found the following, http://activemq.2283324.n4.nabble.com/Old-issue-Memory-leak-after-stop-web-application-in-Tomcat-td4653959.html which referenced the following, https://issues.apache.org/jira/browse/AMQ-3451 I found them both to be informative, and I think a fix was introduced in ActiveMQ 5.7.0, and the end result is that, even though your tomcat/tomee log mentions those possible memory leaks... if you examine your threads 'after' tomcat/tomee is stopped, then you will not see those threads any longer. At least, that is the case for me, since I'm using ActiveMQ 5.8.0 via TomEE+ 1.6.0. :) On Tue, Apr 16, 2013 at 5:22 PM, Leonardo Torres <leonardotorr...@gmail.com>wrote: > Hi guys, > > I´m using AMQ 5.7.0 with Spring 3.0.1 and tomcat 7.0.19 as servlet > container. So, when my application starts, it´s ok, but when the tomcat > stop, I see in the console the follow lines: > > > "SEVERE: The web application [] appears to have started a thread named > [ActiveMQ InactivityMonitor Worker] but has failed to stop it. This is very > likely to create a memory leak. > Apr 16, 2013 2:43:21 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [] is still processing a request that has yet > to finish. This is very likely to create a memory leak. You can control " > > How can I stop these threads ? > > My jms-context.xml (Spring context) : > > <bean id="connectionFactory" > class="org.apache.activemq.ActiveMQConnectionFactory"> > <property name="brokerURL" value="tcp://x.x.x.x:61616?daemon=true"/> > </bean> > > <bean id="poolConnection" > class="org.apache.activemq.pool.PooledConnectionFactory"> > <property name="connectionFactory" ref="connectionFactory"/> > </bean> > > Thank´s in advance > -- > Obrigado > Leonardo Torres. >
