Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
5.13.0
Description
with broker url
failover:(tcp://a:<port>,tcp://b:<port> ")?randomize=false&priorityBackup=true
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