Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6254

Fabric MQ gateway is left in a "no endpoints available" condition after failover, on distributed AWS system

XMLWordPrintable

    • % %
    • Hide

      You can reproduce the issue by:

      • just restarting a slave after the master and slaves are up and running.
      Show
      You can reproduce the issue by: just restarting a slave after the master and slaves are up and running.

      A fabric has an MQ gateway feeding a master-slave pair of brokers. The elements of the fabric are on AWS, and geographically quite widely separated.

      Quite often, after a deliberate switch-over of the master-slave broker roles brought about by shutting down the master, the gateway is left in a broken state where no brokers seem to be available. Although it is normal for this situation to exist transiently during failover, here it seems to be permanent, and a gateway restart is needed to recover service.

              rhn-support-tasato Tadayoshi Sato
              rhn-support-kboone Kevin Boone (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: