activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMQ-6124) failover backup transports do not update the brokerInfo leaving stale org.apache.activemq.ActiveMQConnection#getBrokerName
Date Tue, 12 Jan 2016 13:54:39 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully reassigned AMQ-6124:
-------------------------------

    Assignee: Gary Tully

> 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)

Mime
View raw message