Thanks for pointing this out Laures as we are using 5.5.1. We will definitely add this case to our failure mode testing and use your thread pool workaround if we experience the issue.
I am curious if using the NIO transport as we do makes any difference. I doubt it since it still uses TCP to make the connection for the bridge. -- View this message in context: http://activemq.2283324.n4.nabble.com/Failover-with-networkConnectors-tp4415677p4424713.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
