[
https://issues.apache.org/activemq/browse/AMQ-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2246.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
thanks for the test case.
issue resolved in r773985 a timedout or failed connect attempt needed to close
off the transport to kill the reader thread
> Failover transport causes connection / thread leak when broker is unresponsive
> ------------------------------------------------------------------------------
>
> Key: AMQ-2246
> URL: https://issues.apache.org/activemq/browse/AMQ-2246
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.2.0
> Reporter: Craig Condit
> Assignee: Gary Tully
> Fix For: 5.3.0
>
> Attachments: SlowConnectionTest.java
>
>
> We have observed in a production environment cases where an overloaded
> ActiveMQ broker stops responding to requests in a timely manner --
> connections can be created, but communication is slow enough to trigger
> reconnect.
> Unfortunately, the old connections never get cleaned up, leading to resource
> exhaustion on the both the clients and the broker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
