[AMQ-3451] Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.7.0
• Component/s: JMS client
• Labels: leak resource

Environment

jdk 1.6.0_23 for Linux 64 bit, Ubuntu 11.04
Tomcat 6.0.32
Spring 3.0.5

• Assignee: Claus Ibsen
• Reporter: John Miller
• Created: 14/Aug/11 20:18
• Updated: 16/Feb/17 08:02
• Resolved: 09/Sep/12 08:39

Description

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 ?

Issue Links

• is related to: AMQ-6602 Memory leak when undeploying webapp with ActiveMQ client
• is related to: AMQ-4033 AMQ Broker - Uses custom RMIServerSocketFactory class which cannot be unloaded due socket reuse
• is related to: AMQ-4008 Tomcat WARN on shutdown about ThreadLocal not cleared from log4j
• relates to: AMQ-2852 Memory leak when undeploying webapp with ActiveMQ client
• relates to: AMQ-3962 Memory leak bacause of InactivityMonitor thread
• relates to: AMQ-3959 Memory leak caused by org.apache.activemq.util.StringArrayEditor