Hi Jules,

> This is a full stack dump of a reproducible hang-up in the
> WebIntegration test-suite with Jetty4.
> 
> Note the two threads which seem to be waiting on the same line of
> code....
> 
>  at java.lang.ClassLoader.loadClass(ClassLoader.java:286)
> 
> This looks like a deadlock to me - has anyone else had a 
> similar problem
> ?
> 
> Do any of those org.jboss.system folks have any ideas - or do I put on
> my debugging hat ?

We talked about this some time ago, I guess you're victim of
loadClassInternal...

What would be interesting here is to understand which is the classloader
couple that hangs, ie what are the monitor objects specified by the
sentence "waiting for monitor entry", and what is the CL hierarchy at
that point.

Since I encountered a very similar problem in one of my projects, I
wrote a small utility class that uses JDI to inspect those monitor
objects, and understand who is blocking on what. Of course the problem
should be reproducible (or at least should happen often :). 
If you think the utility class may help you I can lend it to you, just
let me know.

Simon

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to