activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SuoNayi (Updated) (JIRA)" <>
Subject [jira] [Updated] (AMQ-3544) Rebalance does not work well(reproductive)
Date Tue, 15 Nov 2011 15:08:53 GMT


SuoNayi updated AMQ-3544:


Unit test for reproducting the issue.
> Rebalance does not work well(reproductive)
> ------------------------------------------
>                 Key: AMQ-3544
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: SuoNayi
>            Priority: Critical
>              Labels: rebalance
>         Attachments:
> 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:!default.jspa
For more information on JIRA, see:


View raw message