ActiveMQ
  1. ActiveMQ
  2. AMQ-3544

Rebalance does not work well(reproductive)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.5.0
    • Fix Version/s: None
    • Component/s: Broker, JMS client
    • Labels:

      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!

        Activity

        SuoNayi created issue -
        SuoNayi made changes -
        Field Original Value New Value
        Summary Rebalance does not wrok well(reproductive) Rebalance does not work well(reproductive)
        Description 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!
        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!
        SuoNayi made changes -
        Attachment AMQ3544Test.java [ 12503751 ]
        Timothy Bish made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Cannot Reproduce [ 5 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            SuoNayi
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development