Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Cannot Reproduce
-
5.5.0
-
None
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!