Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Sat, 29 Oct 2011 05:33:35 +0000 (UTC)
From: "SuoNayi (Commented) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1957973645.35756.1319866415210.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1331754741.16851.1318666331759.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3544) Rebalance does not work
 well(reproductive)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139120#comment-13139120 ] 

SuoNayi commented on AMQ-3544:
------------------------------

ok,I will reconstruct the test case to make the issue clear.
As far as I know, when a broker is stopping it will close all bridges with others and notify it's current connected brokers to clients,but those current connected brokers are itself now.The clients will be updated by the url of the broker which is stopped ,so the clients will not know those active broker url.
                
> 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