[
https://issues.apache.org/jira/browse/AMQ-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3176.
-----------------------------
Resolution: Fixed
http://svn.apache.org/viewvc?rev=1069339&view=rev
> Potential deadlock in duplex network connector recreation, resulting in
> dangling connections
> --------------------------------------------------------------------------------------------
>
> Key: AMQ-3176
> URL: https://issues.apache.org/jira/browse/AMQ-3176
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: duplex, networkconnector, shutdown
> Fix For: 5.5.0
>
>
> End result is lots of connections that are taking too long to shutdown and in
> particular: {code}2011-02-07 08:56:49,422 | INFO | sport: tcp:///xxx:56982 |
> TransportConnection | The connection to '/xxx:56981' is taking a long time to
> shutdown.
> ....
> 2011-02-07 08:56:49,458 | INFO | sport: tcp:///xxx:56981 |
> TransportConnection | The connection to '/xxx:56982' is taking a long time to
> shutdown.{code} where there is an overlap, with two connections trying to
> stop each other.
> Problem appears when the initiator of a duplex network connector sees a
> failure and trys to reconnect and the responder sees the old transport
> connector in place. It tries to stop the existing connection but does it in a
> sync call so the potential to block and lock is present.
> 2011-01-26 16:35:54,618 [..] INFO TransportConnection - The connection to
> '/xx:51585' is taking a long time to shutdown.
> 2011-01-26 16:35:56,500 [..] INFO TransportConnection - The connection to
> '/xx:51585' is taking a long time to shutdown.{code}
> In particular,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
