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

Sergey edited comment on AMQ-3451 at 8/3/12 12:15 PM:
------------------------------------------------------

I have tried the patch below
-------------------------
Index: 
activemq-core/src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java
===================================================================
--- 
activemq-core/src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java   
    (revision 1366667)
+++ 
activemq-core/src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java   
    (working copy)
@@ -108,6 +108,8 @@
                 Thread thread = new Thread(runnable, name + "-" + 
id.incrementAndGet());
                 thread.setDaemon(daemon);
                 thread.setPriority(priority);
+                thread.setContextClassLoader(null);
                 return thread;
             }
         });
-------------------------

Still have memory leak, now because of inherited access control context, see 
the screenshot.


                
      was (Author: sgri):
    I have tried the patch below
-------------------------
Index: 
activemq-core/src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java
===================================================================
--- 
activemq-core/src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java   
    (revision 1366667)
+++ 
activemq-core/src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java   
    (working copy)
@@ -108,6 +108,8 @@
                 Thread thread = new Thread(runnable, name + "-" + 
id.incrementAndGet());
                 thread.setDaemon(daemon);
                 thread.setPriority(priority);
+                thread.setContextClassLoader(null);
                 return thread;
             }
         });
-------------------------

Still have memory leak, now because of inherited access control context.


                  
> 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: inherited_access_cotrol_context_leak.png, 
> 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