You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/05/03 17:22:16 UTC
[jira] [Resolved] (AMQ-4505) Client doesn't fail over to other
broker if updateClusterClientsOnRemove = true
[ https://issues.apache.org/jira/browse/AMQ-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-4505.
-------------------------------
Resolution: Fixed
Fixed on trunk.
> 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 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