Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-534

Backup Hawt.io management console unavailable after a Master/Slave failover occurs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • A-MQ 7.0.0.ER15
    • None
    • None
    • Hide

      How to create the enviroment:

      1. <ARTEMIS_HOME/>bin/artemis create --replicated --user admin --password admin --role admin --allow-anonymous y --clustered --host 127.0.0.1 --cluster-user clusterUser --cluster-password clusterPassword --name broker1 broker1

      2. <ARTEMIS_HOME/>bin/artemis create --replicated --slave --user admin --password admin --role admin --allow-anonymous y --clustered --host 127.0.0.1 --cluster-user clusterUser --cluster-password clusterPassword --name broker2 broker2

      3. Add the following tag to broker.xml broker1 broker at ha-policy configuration: <check-for-live-server>true</check-for-live-server>

      4. Add the following tag to broker.xml broker2 broker at ha-policy configuration:
      <allow-failback>true</allow-failback>

      Steps to reproduce:

      1. Start broker1 (http://localhost:8161/hawtio)
      2. Start broker2 (http://localhost:8261/hawtio)
      3. Confirm that managment console in both brokers is UP
      4. Stop broker1 (master)
      5. Confirms that managment console of the broker2 is UP and the broker have became the master broker
      6. Start the broker1
      7. Confirm that managment console of the broker1 is UP and the broker1 is the master again
      8. Open the managment console of the broker2 (http://localhost:8261/hawtio) . The managment console is DOWN

      Show
      How to create the enviroment: 1. <ARTEMIS_HOME/>bin/artemis create --replicated --user admin --password admin --role admin --allow-anonymous y --clustered --host 127.0.0.1 --cluster-user clusterUser --cluster-password clusterPassword --name broker1 broker1 2. <ARTEMIS_HOME/>bin/artemis create --replicated --slave --user admin --password admin --role admin --allow-anonymous y --clustered --host 127.0.0.1 --cluster-user clusterUser --cluster-password clusterPassword --name broker2 broker2 3. Add the following tag to broker.xml broker1 broker at ha-policy configuration: <check-for-live-server>true</check-for-live-server> 4. Add the following tag to broker.xml broker2 broker at ha-policy configuration: <allow-failback>true</allow-failback> Steps to reproduce: 1. Start broker1 ( http://localhost:8161/hawtio ) 2. Start broker2 ( http://localhost:8261/hawtio ) 3. Confirm that managment console in both brokers is UP 4. Stop broker1 (master) 5. Confirms that managment console of the broker2 is UP and the broker have became the master broker 6. Start the broker1 7. Confirm that managment console of the broker1 is UP and the broker1 is the master again 8. Open the managment console of the broker2 ( http://localhost:8261/hawtio ) . The managment console is DOWN

      The hawt.io management console of the backup node in a master/slave cluster topology become unavailable after the recovery of the master node in a failover scenario.

              rh-ee-ataylor Andy Taylor
              Asouza@redhat.com Angelo Souza
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: