[
https://issues.apache.org/jira/browse/AMQ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646645#comment-13646645
]
Timothy Bish commented on AMQ-4501:
-----------------------------------
I see one issue so far in Failover transport at least in relation to his test
case. The client uses a string compare of the connected transport URI against
the first in the connect list, which can be different if for instance the
client is configured with "tcp://localhost:61616" and the broker sends the
resolved "tcp://127.0.0.1:61616". In that case the client incorrectly
reconnects thinking it needs to make a change when in fact its already on the
right one.
> 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
> 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
