[jboss-dev-forums] [JBoss Microcontainer Development] - Re: Potential deadlock in ClassLoaderManager
adrian@jboss.org
do-not-reply at jboss.com
Mon Sep 14 14:03:58 EDT 2009
No the problem is on line 205 - unless the first thread with the add() is looping.
It looks like a missed notification since nothing is holding the lock?
| "Thread-2" prio=10 tid=0x83113800 nid=0x443e in Object.wait() [0x833b2000]
| java.lang.Thread.State: WAITING (on object monitor)
| at java.lang.Object.wait(Native Method)
| - waiting on <0x942aa6e0> (a java.util.Collections$SynchronizedList)
| at java.lang.Object.wait(Object.java:485)
| at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:205)
| - locked <0x942aa6e0> (a java.util.Collections$SynchronizedList)
|
If you can reproduce it, can you turn up the logging for
org.jboss.detailed.classloader.ClassLoaderManager
to TRACE.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255167#4255167
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255167
More information about the jboss-dev-forums
mailing list