[QPIDJMS-342] Missed connect error on start can lead to hung failover reconnect cycle

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.26.0
• Fix Version/s: 0.27.0
• Component/s: qpid-jms-client
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 17/Oct/17 18:43
• Updated: 25/Apr/18 10:10
• Resolved: 25/Apr/18 10:10

Description

In some cases where the jms.connectTimeout is tripped during socket level connection and the failover transport bits are in use the client an fall into a reconnect loop or stall waiting for an error callback that won't be triggered.

One workaround exists which is to configure the transport level socket connect timeout to be lower than the jms.connectTimeout value