[
https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447262#comment-13447262
]
Claus Ibsen commented on AMQ-3451:
----------------------------------
The ASF CI server will once in a while deploy a new SNAPSHOT you can download.
Keep an eye on
https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/
The attached patch only fixes on the broker side, there is still all the
transports. I am continuing on the patch, taking one step at a time. Currently
testing with 2 more fixes for discover agent and another place. Then next is
the remainder 7 transports using it.
> 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: AMQ-3451-broker.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
