Gary Tully created AMQ-6124:
-------------------------------
Summary: failover backup transports options do not update the
brokerInfo stale org.apache.activemq.ActiveMQConnection#getBrokerName
Key: AMQ-6124
URL: https://issues.apache.org/jira/browse/AMQ-6124
Project: ActiveMQ
Issue Type: Bug
Components: JMS client
Affects Versions: 5.13.0
Reporter: Gary Tully
Priority: Minor
Fix For: 5.14.0
with broker url {code}failover:(tcp://a:<port>,tcp://b:<port>
")?randomize=false&priorityBackup=true{code} The brokerName as reported by
org.apache.activemq.ActiveMQConnection#getBrokerName stays at A even after
failover to B.
The backup transport are started up front and the brokerInfo is not cached so
it never gets replayed to the jms connection.
The same is true for the backup attribute
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
