activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread
Date Thu, 06 Sep 2012 17:59:08 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449862#comment-13449862
] 

Claus Ibsen commented on AMQ-3451:
----------------------------------

Okay AMQ-4026 is now committed, so we have a better API for shutting down thread pools. Will
work on getting the patches in the codebase, so the JMS Client work well in Tomcat when re-deploying
apps. 

A fully embedded ActiveMQ broker in Tomcat has a number of more pools and other parts in the
works, eg such as JMX and whatnot that can cause a bit pain, eg to ensure all JMX stuff is
properly unregistered and whatnot. 

First priority is the JMS client though.
                
> 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

Mime
View raw message