Using failover: with static discovery in a network connector to choose from a
master/slave tuple leads to hangs and invalid states
----------------------------------------------------------------------------------------------------------------------------------
Key: AMQ-3542
URL: https://issues.apache.org/jira/browse/AMQ-3542
Project: ActiveMQ
Issue Type: Bug
Components: Connector, Transport
Affects Versions: 5.5.0, 5.4.2
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.6.0
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
