Why broker log continuous throws error about 'amq shutting down NC' when networkConnectors are used?

Solution Verified - Updated -

Issue

I have a Master/Slave AMQ setup with shared NFS folder for KahaDB storage. When I start the server, the server logs continuous throw below errors:

2019-09-19 09:30:45,175 | INFO  | iveMQ Task-14848 | DiscoveryNetworkConnector        | etwork.DiscoveryNetworkConnector  120 | 162 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-630283 | Establishing network connection from vm://amq to tcp://<backup AMQ server IP address>:61616
2019-09-19 09:30:45,177 | INFO  | e[amq] Task-5816 | DemandForwardingBridgeSupport    | rk.DemandForwardingBridgeSupport 1067 | 162 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-630283 | amq Shutting down NC
2019-09-19 09:30:45,178 | INFO  | e[amq] Task-5816 | DemandForwardingBridgeSupport    | rk.DemandForwardingBridgeSupport  321 | 162 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-630283 | amq bridge to Unknown stopped
2019-09-19 09:30:45,179 | WARN  | iveMQ Task-14848 | DiscoveryNetworkConnector        | etwork.DiscoveryNetworkConnector  165 | 162 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-630283 | Could not start network bridge between: vm://amq and: tcp://<backup AMQ server IP address>:61616 due to: Connection refused

Environment

  • Red Hat AMQ
    • 6.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