Yah, looks like it *could* be a race between when the remote part of the bridge is up and when the broker is trying to forward a message. It would be best if you can write a junit test and attach to the aforementioned JIRA. Take a look at the following for help with writing the test.
http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/ThreeBrokerQueueNetworkTest.java?view=markup On Tue, Jun 4, 2013 at 8:42 AM, matteor <matteo.ru...@abodata.com> wrote: > It happens when we try to add a third broker to the network and after few > seconds we stop the newly introduced broker. > This third broker has the same configuration with respect broker 2. > > matteo > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Occasional-Null-Pointer-Exception-during-NetworkConnector-connection-again-tp4667796p4667819.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
