[
https://issues.apache.org/jira/browse/AMQ-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137373#comment-13137373
]
Timothy Bish commented on AMQ-3544:
-----------------------------------
I was never able to reproduce the issue with the test case given. You might
want to try and tweak it somewhat to see if you can make the issue appear, in
any event, adding the issue here and checking the grant license to Apache box
will allow us to include it in the unit tests should we find a way to reproduce
and fix the issue.
> Rebalance does not work well(reproductive)
> ------------------------------------------
>
> Key: AMQ-3544
> URL: https://issues.apache.org/jira/browse/AMQ-3544
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
> Affects Versions: 5.5.0
> Reporter: SuoNayi
> Priority: Critical
> Labels: rebalance
>
> Assuming there are two networked brokers A and B in both direction and enable
> both brokers to rebalance client via three properties, updateClusterClients,
> updateClusterClientsOnRemove and rebalanceClusterClients.
> Now setting up a client whose broker url is Broker A to connect to Broker A
> and make sure the client has connected to Broker A via log information(you
> can change the log level to be debug level).
> Shutdown Broker A and expect for that the client will failover to Broker B
> but it will try to connect Brork A continually and does not know there is
> Broker B available at all!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
