activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SuoNayi (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3544) Rebalance does not work well(reproductive)
Date Tue, 18 Oct 2011 02:06:10 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

SuoNayi updated AMQ-3544:
-------------------------

    Description: 
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!


  was:
Assuming there are two networked brokers A and B in both direction and specify both brokers
to enable to rebalance client via three properties, updateClusterClients, updateClusterClientsOnRemove
and rebalanceClusterClients.

Now setting up a client which 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!

        Summary: Rebalance does not work well(reproductive)  (was: Rebalance does not wrok
well(reproductive))
    
> 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

        

Mime
View raw message