[
https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450678#comment-13450678
]
Claus Ibsen commented on AMQ-3451:
----------------------------------
Okay got further on the embedded broker side. Got a classloader leak fixed due
a spring introspection cache, needed to be explicit cleared.
The tomcat manager console now says there is no leaks. And all activemq and
camel classes is fully unloaded when stopping the app.
One last thing would be a JMX thread not being shutdown on the broker side.
> Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread
> -------------------------------------------------------------------
>
> Key: AMQ-3451
> URL: https://issues.apache.org/jira/browse/AMQ-3451
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.5.0
> Environment: jdk 1.6.0_23 for Linux 64 bit, Ubuntu 11.04
> Tomcat 6.0.32
> Spring 3.0.5
> Reporter: John Miller
> Assignee: Claus Ibsen
> Labels: leak, resource
> Attachments: activemq-core-5.7-SNAPSHOT.jar, AMQ-3451-broker2.patch,
> AMQ-3451-broker.patch, AMQ-3541-3.patch,
> inherited_access_cotrol_context_leak.png, patch.txt, transport_thread_leak.png
>
>
> Every time when restarting web application in Tomcat Manager I get messages:
> SEVERE: The web application [/sms] appears to have started a thread named
> [ActiveMQ Task-3] but has failed to stop it. This is very likely to create a
> memory leak.
> With every restart PermGen space is increased and finally i got OutOfMemory
> error for PermGen space.
> I use Spring DefaultMessageListenerContainer, and it's shutdown method closes
> properly receivers threads. What is "ActiveMQ Task-3" thread and how to close
> it properly ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
