DemandForwardingBridgeSupport is not reconnecting properly

Solution Verified - Updated -


We are using 5.7.0.fuse-71-047 with network connectors between master/slave pairs in non-duplex mode. Pair 1 opens a bridge to Pair 2, and vice versa. In a case that one of pairs is not available, the network connector seems to give up and shutdown after about a minute and a half.

Pair one: configuration activemq.xml:
 <networkConnector uri="masterslave:(tcp://amq2:61616,tcp://amq4:61616)" />

Pair two: configuration activemq.xml:
 <networkConnector uri="masterslave:(tcp://amq1:61616,tcp://amq3:61616)" />

The logs show that the masterslave uri resolves to:


Why does it say 0?


  • Fuse Message Broker 5.7.X, 5.8.X

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