You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "John Miller (JIRA)" <ji...@apache.org> on 2011/08/15 12:43:27 UTC
[jira] [Closed] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ
5.5 doesn't shutdown a thread
[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Miller closed AMQ-3451.
----------------------------
Duplicate
> 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
> Labels: leak, resource
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira