Start with the basics for any network connectivity issue: Is ActiveMQ running on that host and port? Are clients able to connect to that broker directly using that URI? Are there any firewalls between the machines your two brokers are running on that might be stopping traffic? Are authentication credentials required by that broker, and if so, are you providing them?
On Wed, Oct 8, 2014 at 10:59 AM, urvishamin <urvish.a...@nielsen.com> wrote: > We are getting following WARN message in log file. It looks like clustering > is not working. We started getting this error after upgrading Active MQ to > 5.4.3. > Configuration: Active MQ 5.4.3 > Spring Framework > Jboss 4.2.3 CP6 > > 2014-10-07 15:39:38,625 WARN > [org.apache.activemq.network.DiscoveryNetworkConnector] Could not start > network bridge between: vm://localhost?async=false&network=true and: > tcp://10.7.205.47:61616 due to: java.net.ConnectException: Connection > refused > > > Please let us know how to resolve the issue. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Getting-warn-message-Could-not-start-network-bridge-between-vm-localhost-async-false-network-true-and-tp4686238.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
