Fabric8 MQ gateway is left in a "no endpoints available" state

Solution Verified - Updated -

Issue

In various circumstances involving restarting Fabric8 containers, or network outages involving communication between containers, the Fabric8 MQ gateway fails to detect a master broker. The problem persists even after the original cause has been removed. Connection attempts to the MQ gateway are rejected, and the gateway log shows "no endpoints available."

Environment

  • Red Hat JBoss Fuse
    • 6.3 and earlier
  • Broker environment managed by Fabric8
  • Fabric8 MQ gateway

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content