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

Gary Tully commented on AMQ-3451:
---------------------------------

@Sergey this is great information

So the crux seems to be the classloader reference, if the pool is to be shared 
then it must not refer to an app specific loader. Do you understand the nature 
of that reference?

The alternative approach is to remove the use of the statically defined default 
task runner factory from client side code and use one per connection factory.
                
> 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
>         Attachments: 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to