[
https://issues.apache.org/jira/browse/AMQ-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653459#comment-13653459
]
Carlos de la Torre commented on AMQ-4505:
-----------------------------------------
Hi Timothy, It looks that I've found another issue when you have an HA pair
with shared storage, this time is failing to failover even if
updateClusterClientsOnRemove=false. Could you please point me to your HA test
cases so I can try to reproduce it there (I couldn't find them)?
Probably the changes to this bug fixes the issue I just found, but I want to
have a test case so we make sure is fixed in 5.9.
Thanks in Advance.
> 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
