[
https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686031#comment-13686031
]
Timothy Bish commented on AMQ-4586:
-----------------------------------
Part of the trouble here is that the getConnection method doesn't do anything
if the conn.start() fails so the connection is never closed.
I'm not sure if there's any async exceptions that are recoverable or not, if so
then closing the down the executor would be bad.
> 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
