connectors.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4685246.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
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
the same
thread.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4685180.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
to the discussion
> below:
>
> http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4684969.html
> To unsubscribe from JMS to JMS bridge reconnection dispatching not
> working in simple conditions, click here
>
, the next step that I would try is grabbing a stack trace.
Is you don't want to do that, no worries. Other than leading to the
annoyance of needing a kill -9, is there any other impact?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnec
ge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4684969.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
issuing "kill -9".
I never see anything in the logs that would signal bigger issues at all.
I this a known issue? Do you guys see any obvious explanation in the
configuration of the producer/consumes or brokers (I certainly don't)?
Help would be greatly appreciated.
--
View th
