[
https://issues.apache.org/jira/browse/QPID-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher closed QPID-4435.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.19
> Reconnect on connect failure hangs at third address to try
> ----------------------------------------------------------
>
> Key: QPID-4435
> URL: https://issues.apache.org/jira/browse/QPID-4435
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Environment: Linux
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.19
>
>
> Necessary conditions to trigger hang:
> * You are connecting to a name that resolves to 3 or more underlying network
> addresses.
> * The first 2 addresses refuse the connection (there is no daemon listening
> on the appropriate port at that address).
> In this case the client will attempt to connect to the third resolved
> address, but will hang forever waiting.
> If you look at a server log that is listening on the third address then you
> will eventually see:
> ... error Connection ... No protocol received closing
> because the server has received the connection and made the initial reply but
> has not heard back in the alloted time.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
