I recommend using camel to route between the embedded brokers and the central
brokers. Networks of brokers lead to many problems, and static routing is
the best way to avoid them. Avoiding the demand-forwarding bridge is also
important.
--
View this message in context:
http://activemq.2283324
Hmm, it looks like there are two reentrant locks.
Are there 2 brokers running in the same JVM connecting over a network
connector with the VM transport?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-condi
Good catch. Something looks very wrong with this deadlock picture. Both
threads are blocking on this call:
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66)
Which is this instruction:
writeLock.lock();
Which is this method call:
java.util.concurrent.locks.
