[
https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Posta updated AMQ-4586:
---------------------------------
Attachment: AMQ-4586-fix2.patch
AMQ-4586-fix1.patch
Two options for fixes.
#1 explicitly shuts down the ThreadPoolExecutor when
AciveMQConnection#onException is called (after the transport is disposed)
#2 the second reduces the core thread pool from 1 to 0 and the thread will be
clean up after the cleanup time (5s).
Thoughts? Any other suggestions?
When using failover, we don't see this case come up.
> ActiveMQConnection leaks executor threads onException
> -----------------------------------------------------
>
> Key: AMQ-4586
> URL: https://issues.apache.org/jira/browse/AMQ-4586
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.8.0
> Reporter: Christian Posta
> Attachments: AMQ-4586-fix1.patch, AMQ-4586-fix2.patch,
> ClientConnectionThreadLeakTest.java
>
>
> When a broker goes down, and client is not using failover transport, the
> client can experience leaked threads because the executor is not properly
> cleaned up. The symptoms of this are seeing "ActiveMQ Connection Executor"
> threads staying around.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
