[AMQ-3542] Using failover: with static discovery in a network connector to choose from a master/slave tuple leads to hangs and invalid states

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.2, 5.5.0
• Fix Version/s: 5.6.0
• Component/s: Connector, Transport
• Labels: failover master network slave
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 13/Oct/11 19:33
• Updated: 30/Apr/12 10:08
• Resolved: 13/Oct/11 20:23

Description

static discovery will try to connect to all provided urls. When the list is a master/slave pair with shared storage, only one will active, leading log messages indicating repeated failure to connect.
A potential solution is to use failover: just to pick a url but let it delegate failover to the network connector such that the network bridge is correctly stopped/restarted.
static:(failover:(tcp://a:61616,tcp://slave:61616)?maxReconnectAttempts=..)
This does not work reliably atm, due to inconsistency in the failover reconnect logic, a network connectors interest in transport interruption/resumption and the lack of thread safety in tracking existing bridges.

Issue Links

• relates to: AMQ-3575 Failover transport race condition causes intermittent incomplete bridge connections