[
https://issues.apache.org/jira/browse/AMQ-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986563#comment-13986563
]
Gary Tully commented on AMQ-4505:
---------------------------------
related test case at:
https://github.com/apache/activemq/blob/20f384ce59b758a0f3c1b0e0620e2efd58ca230a/activemq-unit-tests/src/test/java/org/apache/activemq/transport/failover/FailoverComplexClusterTest.java
> Client doesn't fail over to other broker if updateClusterClientsOnRemove =
> true
> -------------------------------------------------------------------------------
>
> Key: AMQ-4505
> URL: https://issues.apache.org/jira/browse/AMQ-4505
> 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
> Priority: Critical
> Fix For: 5.9.0
>
> Attachments: AMQ-4505-TestcaseToReproduce.patch
>
>
> When a cluster of brokers have updateClusterClients="true"
> rebalanceClusterClients="true" updateClusterClientsOnRemove="true" in the
> transport connector and a client connects including only one broker address.
> If the broker the client is connected to stops, it doesn't failover to the
> other ones.
> This happens when updateClusterClientsOnRemove=true, if it's false client
> fails over to the other brokers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
