activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1252) transport won't shutdown, stuck in countdownlatch
Date Mon, 08 Sep 2008 14:55:56 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully updated AMQ-1252:
----------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> transport won't shutdown, stuck in countdownlatch
> -------------------------------------------------
>
>                 Key: AMQ-1252
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1252
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>            Reporter: Alex Burgel
>             Fix For: 5.3.0
>
>
> i have a network of brokers setup. when i shutdown the brokers, one of them always gets
stuck waiting. i've pasted the relevant part of a thread dump below. you can see that the
tcp transport is stuck waiting for the connection to host 10.4.7.108 to start up. the problem
is that this host has already been shutdown. so the other host will be stuck waiting forever.
> this post seems to be relevant to the issue:
> http://www.nabble.com/Network-connector-failover-problems-tf3659372s2354.html#a10275742
> "ActiveMQ Transport: tcp:///10.4.7.108:40623" prio=1 tid=0xb08f28a8 nid=0x4f84 waiting
on condition [0x8490a000..0x8490a500]
>         at sun.misc.Unsafe.park(Native Method)
>         at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:681)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:837)
>         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1144)
>         at edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(CountDownLatch.java:207)
>         at org.apache.activemq.network.DemandForwardingBridgeSupport.waitStarted(DemandForwardingBridgeSupport.java:842)
>         at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:332)
>         at org.apache.activemq.network.DemandForwardingBridgeSupport$2.onCommand(DemandForwardingBridgeSupport.java:131)
>         at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:95)
>         at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
>         at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
>         at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
>         at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>         at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
>         at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message