Hello!

I'm running web application with embedded ActiveMQ 5.4.1 and Spring
3.0.5 with Tomcat 6.0.29.

When I undeploy web application Tomcat says:

INFO: ActiveMQ Message Broker (localhost,
ID:pc-karev.cpr.jet.msk.su-36622-1290758921941-0:0) is shutting down
26.11.2010 11:11:06 org.apache.activemq.broker.TransportConnector stop
INFO: Connector vm://localhost Stopped
26.11.2010 11:11:06
org.apache.activemq.broker.scheduler.JobSchedulerStore doStop
INFO: JobSchedulerStore:activemq-data/localhost/scheduler stopped
26.11.2010 11:11:06 org.apache.activemq.store.kahadb.plist.PListStore doStop
INFO: PListStore:activemq-data/localhost/tmp_storage stopped
26.11.2010 11:11:06 org.apache.activemq.store.kahadb.KahaDBStore doStop
INFO: Stopping async queue tasks
26.11.2010 11:11:06 org.apache.activemq.store.kahadb.KahaDBStore doStop
INFO: Stopping async topic tasks
26.11.2010 11:11:06 org.apache.activemq.store.kahadb.KahaDBStore doStop
INFO: Stopped KahaDB
26.11.2010 11:11:06 org.apache.activemq.broker.BrokerService stop
INFO: ActiveMQ JMS Message Broker (localhost,
ID:pc-karev.cpr.jet.msk.su-36622-1290758921941-0:0) stopped
26.11.2010 11:11:06 org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named
[VMTransport] but has failed to stop it. This is very likely to create
a memory leak.
26.11.2010 11:11:06 org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named
[VMTransport] but has failed to stop it. This is very likely to create
a memory leak.
26.11.2010 11:11:06 org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named
[VMTransport] but has failed to stop it. This is very likely to create
a memory leak.
26.11.2010 11:11:06 org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named
[ActiveMQ Task] but has failed to stop it. This is very likely to
create a memory leak.

It is a problem in ActiveMQ or in my configuration?

Spring application context with ActiveMQ configuration is here:
https://github.com/maxcom/lorsource/blob/1df502d66bc74084256d259d11c90552ae9c0754/web/WEB-INF/applicationContext.xml

best wishes, Max

Reply via email to