[QPID-3691] Failover should sync once before indicating successfully failing comepletion

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.15
• Fix Version/s: 0.15
• Component/s: JMS AMQP 0-x
• Assignee: Andrew MacBean
• Reporter: Keith Wall
• Created: 16/Dec/11 11:31
• Updated: 14/Mar/17 20:08
• Resolved: 16/Dec/11 13:00

Description

On failover, the Java client completes all resubscription activities (producers, consumers) without performing a 0-10 sync. This approach means that if for some reason resubscriptions fails, the client is not aware of the problem until next use.

The client should be changed to call sync() once before reporting a successful failover via ConnectionListener#failoverComplete().

This problem has been exposed by QPID-3683.

Issue Links

• is required by: QPID-3683 FailoverBehaviourTest.testPublishClientAcknowledgedWithFailoverMutex/testPublishTransactedAcknowledgedWithFailoverMutex failing regularly on Jenkins.