FUSE Message Broker 5.3 release no longer appears to accept connections from anything other than local clients.

Solution Verified - Updated -

Environment

  • Fuse Message Broker 5.3 and higher

Issue

FUSE Message Broker 5.3 release no longer appears to accept connections from anything other than local clients.

Unable to connect to Message Broker with remote clients.

Resolution

Use an ip address or the real hostname or the wildcard address of 0.0.0.0. The latter tells the broker to listen on all available network cards.

Change the transportConnector uri not to use "localhost".
Instead, use "0.0.0.0" to allow remote connections. see the example config below:

<transportConnectors>
  <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" />
  <transportConnector name="ssl" uri="ssl://localhost:61617"/>
  <transportConnector name="xmpp" uri="xmpp://localhost:61222"/>
  <transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
</transportConnectors>

Root Cause

There is a change of behavior between Message Broker 5.2 and 5.3. See the section : "Change of behavior for multihomed hosts using "tcp://localhost" in the 5.3.0.1 release note .
Windows treats the loopback address and regular internet address as separate network interfaces so it is multihomed by default. localhost typically means the loopback interface.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.