[jira] [Commented] (AMQ-6124) failover backup transports do not update the brokerInfo leaving stale org.apache.activemq.ActiveMQConnection#getBrokerName

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093916#comment-15093916 ] 

ASF subversion and git services commented on AMQ-6124:
------------------------------------------------------

Commit db1506a5921f70134c3b647cec51204f0e1c1416 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=db1506a ]

https://issues.apache.org/jira/browse/AMQ-6124 - fix and test - propagate broker info from prestarted backup transport


> failover backup transports do not update the brokerInfo leaving 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
>            Assignee: Gary Tully
>            Priority: Minor
>              Labels: backup, failover, priorityBackup
>             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)