Fuse Message Broker; remote client "Could not connect to broker"

Solution Verified - Updated -

Issue

  • After upgrade from Fuse Message Broker 5.2 to 5.3, client receives the following exception:

"DefaultMessageListenerContainer 804 | Could not refresh JMS Connection for destination 'test.job.queue1' - retrying in 5000 ms. Cause: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused: connect"
  • remote client cannot connect to broker that uses "localhost" in its Transport Connector definition.

Environment

  • Fuse Message Broker/ActiveMQ 5.3

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