[QPID-3912] Client failover fails to reconnect if a previous attempted reconnection has failed 'late' in the connection start process.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.17
• Fix Version/s: 0.17
• Component/s: JMS AMQP 0-x
• Assignee: Keith Wall
• Reporter: Keith Wall
• Created: 23/Mar/12 13:52
• Updated: 14/Mar/17 20:12
• Resolved: 12/Sep/12 21:40

Description

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.

Issue Links

• relates to: QPID-4289 [Java Client 0-8/0-9.x] Failover functionality sometimes does not restore the connection