[A-MQ] Network Bridge between ActiveMQ brokers not automatically re-established after an exception.

Solution Verified - Updated -

Issue

We connect two ActiveMQ broker instances through a secure network bridge. The network connector configuration reads:

<networkConnectors>
  <networkConnector uri="masterslave:(ssl://localhost:62616,ssl://localhost:61629)" name="broker1-to-broker2" />
</networkConnectors>

The target broker (to which the network bridge is established) uses an nio+ssl transport listener, e.g.

<transportConnector name="openwire" uri="nio+ssl://0.0.0.0:62616"/>

The target broker also uses the JDBCIOExceptionHandler, as per

<ioExceptionHandler>
  <jDBCIOExceptionHandler stopStartConnectors="true"/>
</ioExceptionHandler>

Now, if the target broker encounters an exception from the persistence store, e.g.

java.sql.SQLException: org.apache.commons.dbcp.DelegatingPreparedStatement with address: "oracle.jdbc.driver.OraclePreparedStatementWrapper@2a270cd1" is closed.

it shuts down and restarts its transport connector, which also shuts down the network bridge between the two ActiveMQ broker instances.
However the network bridge does not get re-established automatically once the target broker has restarted its transport.
There are no errors or warning in the broker log files that would indicate why the network bridge could not get re-established.

  • Bridge disconnect

Environment

  • JBoss A-MQ 6.2.1
  • JBoss A-MQ 6.3 GA

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

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