[
https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-4501.
-------------------------------
Resolution: Fixed
Assignee: Timothy Bish
Fixed on trunk. In practice its fine to have the clients updated with new
brokers but you really don't want to combine priority backup and cluster
rebalance as the clients that are on the priority backup will ignore any
rebalance requests.
> Failover priorityBackup doesn't work if client accepts updates to its list of
> known URIs from the broker.
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4501
> URL: https://issues.apache.org/jira/browse/AMQ-4501
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.8.0
> Environment: Mac OSX 10.6.8
> java version "1.6.0_43"
> Reporter: Carlos de la Torre
> Assignee: Timothy Bish
> Fix For: 5.9.0
>
> Attachments: AMQ-4501-TestcaseToReproduce.patch
>
>
> If a client has priorityBackup enabled and connects to a broker in a cluster
> with updateClusterClients="true" in its transport connector, the client
> ignores the priorityBackup flag it connects to any URI received from the
> broker, even if that URI doesn't have priority.
> This is easy to reproduce adding a test case to the
> activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverPriorityTest.java
> test suite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
