activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric-AWL <eric.vinc...@atosorigin.com>
Subject Re: connection.close(), on a brokenConnection resolves my problem
Date Sat, 04 Jul 2009 15:17:17 GMT

"Multicast Discovery Agent Notifier" daemon prio=10 tid=0x000000000a82dc00
nid=0x6586 waiting on condition [0x0000000043188000..0x0000000043188b90] 
   java.lang.Thread.State: WAITING (parking) 
        at sun.misc.Unsafe.park(Native Method) 
        - parking to wait for  <0x00002aaab3cf20a8> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) 
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) 
        at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1978)

        at
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:386) 
        at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043) 
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103) 
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 
        at java.lang.Thread.run(Thread.java:636) 


It seems there is not any executor.shutdown() call in
MulticastDiscoveryAgent Class .... Perhaps, it could be useful to add such a
call in the stop() method ...


-- 
View this message in context: http://www.nabble.com/Do-you-know-when-ActiveMQ-Session-threads-die---tp24071802p24335452.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message