Details
Description
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.
Attachments
Issue Links
- requires
-
AMQ-2852 Memory leak when undeploying webapp with ActiveMQ client
- Resolved