[jira] [Updated] (AMQ-4501) Failover priorityBackup doesn't work if client accepts updates to its list of known URIs from the broker.

["Carlos de la Torre (JIRA)" <ji...@apache.org>]

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

Carlos de la Torre updated AMQ-4501:
------------------------------------

    Attachment: AMQ-4501-TestcaseToReproduce.diff

This test case is very similar to testPriorityBackup. The only difference is that when the transport connectors are created, the cluster flag is set to true which basically creates the connector with updateClusterClients="true" rebalanceClusterClients="true" updateClusterClientsOnRemove="true".
                
> 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, 5.9.0
>         Environment: Mac OSX 10.6.8
> java version "1.6.0_43"
>            Reporter: Carlos de la Torre
>             Fix For: 5.8.0, 5.9.0
>
>         Attachments: AMQ-4501-TestcaseToReproduce.diff
>
>
> 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