Actually it has caused problems with my integration test environments because is completely unexpected and Spring doesn't now about kill -9, it only knows about calling the shutdown hooks.
I ran JConsole and immediately detected this deadlock: Name: ActiveMQ Transport: tcp://localhost/127.0.0.1:61618@55559 State: WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@4b2d19f2 owned by: ActiveMQ BrokerService[localhost-b2] Task-3 Total blocked: 1 Total waited: 3 Stack trace: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197) java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214) java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290) org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66) org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1370) org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:889) org.apache.activemq.broker.TransportConnection.dispatchSync(TransportConnection.java:849) org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:150) org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116) org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) org.apache.activemq.transport.vm.VMTransport.doDispatch(VMTransport.java:138) org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:130) - locked java.util.concurrent.atomic.AtomicBoolean@c7d2c2b org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:107) org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68) org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81) org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:86) org.apache.activemq.network.DemandForwardingBridgeSupport.addSubscription(DemandForwardingBridgeSupport.java:905) org.apache.activemq.network.DemandForwardingBridgeSupport.addConsumerInfo(DemandForwardingBridgeSupport.java:1178) org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteConsumerAdvisory(DemandForwardingBridgeSupport.java:763) - locked java.net.URI@10efd3fa org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:614) org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224) org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116) org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) org.apache.activemq.transport.failover.FailoverTransport$3.onCommand(FailoverTransport.java:208) org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113) org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270) org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214) org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) java.lang.Thread.run(Thread.java:745) Name: ActiveMQ BrokerService[localhost-b2] Task-3 State: WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@4d6775bd owned by: ActiveMQ Transport: tcp://localhost/127.0.0.1:61618@55559 Total blocked: 0 Total waited: 127 Stack trace: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197) java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214) java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290) org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:66) org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) org.apache.activemq.network.DemandForwardingBridgeSupport.serviceLocalCommand(DemandForwardingBridgeSupport.java:1023) org.apache.activemq.network.DemandForwardingBridgeSupport$2.onCommand(DemandForwardingBridgeSupport.java:206) org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116) org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) org.apache.activemq.transport.vm.VMTransport.doDispatch(VMTransport.java:138) org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:130) - locked java.util.concurrent.atomic.AtomicBoolean@14dc51c8 org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:107) org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68) org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60) org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1370) org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:889) org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:935) org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133) org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) On Fri, Aug 22, 2014 at 9:41 PM, pollotek [via ActiveMQ] < ml-node+s2283324n4684969...@n4.nabble.com> wrote: > I ran the same topology with everything in the same server, both brokers, > producer and multi-threaded consumer. I can reproduce this EVERY SINGLE > TIME. > > I tried with 5.9.1 and see exactly the same behavior. I tried with 5.6 > (which is the version I run in production) where I know this basic topology > works and confirmed that it does in fact work. I use exactly the same > configuration on 5.10, 5.9.1 and 5.6 since it seems quite simple. > > I think my topology is pretty basic for a Network of Brokers in a > production environment, I'm pretty surprised it doesn't work. > > Am I missing something here? Is there a flag I missed in my configuration? > Is there a migration guide that I didn't see? > > I can supply test cases for this, logs, heap dumps or thread dumps if it > helps getting this fixed. > > ------------------------------ > If you reply to this email, your message will be added 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 > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4684887&code=Y2xhdWRpby5zYW50YW5hQGdtYWlsLmNvbXw0Njg0ODg3fC0xNTA0MDM5ODky> > . > NAML > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4685158.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
