activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2852) Memory leak when undeploying webapp with ActiveMQ client
Date Wed, 15 Dec 2010 12:47:02 GMT

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

Gary Tully commented on AMQ-2852:
---------------------------------

additional broker improvements in r1049527 - have discovery agent and network connector delegate
to the common pool that can be explicitly shutdown.

> Memory leak when undeploying webapp with ActiveMQ client
> --------------------------------------------------------
>
>                 Key: AMQ-2852
>                 URL: https://issues.apache.org/jira/browse/AMQ-2852
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.3.2
>            Reporter: Daniel Spilker
>            Assignee: Gary Tully
>             Fix For: 5.5.0
>
>
> I have a web app with an ActiveMQ client. When undeploying the app, Tomcat logs the following
messages.
> {code}
> 28.07.2010 17:44:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SCHWERWIEGEND: The web application [] appears to have started a thread named [InactivityMonitor
Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@c821ef] but has failed to stop
it. This is very likely to create a memory leak. 
> 28.07.2010 17:44:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SCHWERWIEGEND: The web application [] appears to have started a thread named [TcpSocketClose:
java.util.concurrent.ThreadPoolExecutor$Worker@19ac2e3] but has failed to stop it. This is
very likely to create a memory leak. 
> {code}
> Searching for "InactivityMonitor Async Task" and "TcpSocketClose", I found org.apache.activemq.transport.tcp.TcpTransport
and org.apache.activemq.transport.InactivityMonitor which both start a ThreadPoolExecutor
in their static intializers but never stop them. The ThreadPoolExecutors hold references to
ActiveMQ classes which hold a reference to the webapp classloader. These references prevent
the webapp classes from being unloaded when the webapp is undeployed. Due to this the servlet
container runs out of memory after a few redeployments.
> The ActiveMQ client should dispose all resources when being closed, including the ThreadPoolExecutors.
Or to provide some methods to explicitly stop these Threads (like org.apache.activemq.thread.Scheduler.shutdown()
does).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message