[
https://issues.apache.org/jira/browse/QPID-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-3912.
----------------------------------
Resolution: Fixed
Resolving this issue, I believe the changes in QPID-4289 address the above
re-opening, and changes were made for this JIRA and included in 0.18 which is
now released os no furhter change should go against this JIRA either way.
> Client failover fails to reconnect if a previous attempted reconnection has
> failed 'late' in the connection start process.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3912
> URL: https://issues.apache.org/jira/browse/QPID-3912
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.17
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: 0.17
>
>
> A client uses failover to allow their client to reconnect to a second broker
> in the event of failure of the primary.
> There is a defect in the Qpid Java client's failover code that means if an
> attempted reconnection fails 'late' in the connection start process, then the
> AMQConnection _closed flag get set permanently to true and this prevents all
> future use of the AMQConnection object, even after a successful reconnection.
> By 'late' I mean a failure after the TCP/IP connection has been successfully
> established - such as an authentication or authorisation problem that causes
> the Broker to decide to close the connection.
> The problem affects both 0-10 and 0-8..0-9-1 code paths.
--
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]
