[
https://issues.apache.org/jira/browse/AMQ-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2138.
-----------------------------
Resolution: Fixed
Assignee: Gary Tully
The fix for https://issues.apache.org/jira/browse/AMQ-2852 will sort this.
> Memory Leak in ActiveMQConnection
> ---------------------------------
>
> Key: AMQ-2138
> URL: https://issues.apache.org/jira/browse/AMQ-2138
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Environment: Tomcat 6 + ActiveMQ 5.1
> Reporter: Markus Wolf
> Assignee: Gary Tully
> Fix For: 5.5.0
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> We discovered a memory leak in the ActiveMQConnection class.
> In our setup we have an activemq 5.1 embedded in our webapplication. On
> undeployemnt (more specially on connection close) the ThreadPoolExecutor is
> kept in memory and could not be garbage collected, because of the
> ThreadFactory which is loaded by our webapp classloader. A reference to it is
> held by the ThreadPoolExecutor.
> This is likly a bug in the JDK TheadPoolExecutor but it could be fixed by
> setting a default ThreadFactory before shutdown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
