Though I've never experienced this, I think this is the problem scenario:
The players:
UnifiedClassLoader A (can load directly class foo)
UnifiedClassLoader B (can load directly class bar)
Thread 1 (context loader is A):
Load new class bar:
- synchronize on UCL A
- Search UCL B
- Attempt to synchronize on UCL B
Thread 2 (contect loader is B):
Load new class foo:
- synchronize on UCL B
- Search UCL A
- Attempt to synchronize on UCL A
Can someone verify if this is accurate?
-Larry
> Ok,
>
> I am sure we can find something.
>
> I would appreciate a brief description of a CL deadlock scenario due to
the
> final loadClassInternal. Jung? Sacha?
>
> It's only software, software is dumb
>
> marcf
>
> xxxxxxxxxxxxxxxxx
> Marc Fleury, Ph.D
> President and CEO
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxx
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
