On 23 June 2010 16:46, Rajith Attapattu <[email protected]> wrote: > Everytime a test gets stuck I see a whole bunch of threads from the > MINANetworkDriver. > Probably due to threads not being cleaned up properly in shutdown. > Best case this maybe due to a bug in the test, but in worst case this > maybe a bug in the MINANetworkDriver itself. > Therefore I think it's best to investigate this matter. > > ex. > "MINANetworkDriver(Client)-org.apache.qpid.transport.network.mina.MINANetworkDriverTest-6" > daemon prio=10 tid=0x0000002ae236fc00 nid=0x3b1a in Object.wait() > [0x0000000043b64000..0x0000000043b64cb0] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000002a9fbc21c0> (a > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock) > at java.lang.Object.wait(Object.java:485) > at > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:316) > - locked <0x0000002a9fbc21c0> (a > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:493) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:689) > at java.lang.Thread.run(Thread.java:619) > > > "MINANetworkDriver(Acceptor)-5" daemon prio=10 tid=0x0000002ae26fe000 > nid=0x3b18 in Object.wait() [0x0000000043962000..0x0000000043962db0] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000002a9f9df0c0> (a > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock) > at java.lang.Object.wait(Object.java:485) > at > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:316) > - locked <0x0000002a9f9df0c0> (a > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:493) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:689) > at java.lang.Thread.run(Thread.java:619) > > > "AnonymousIoService-2" daemon prio=10 tid=0x0000002ae55b2800 > nid=0x4203 in Object.wait() [0x000000004244d000..0x000000004244da30] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x0000002adafc7b20> (a > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock) > at java.lang.Object.wait(Object.java:485) > at > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:316) > - locked <0x0000002adafc7b20> (a > edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:493) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:689) > at java.lang.Thread.run(Thread.java:619) > > > > -- > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected]
I've been testing a change to the tests which seems to be making it more reliable... but just haven't had enough time recently to investigate. Hope to get to it this week though. Martin -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
