|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?
If this is the case this is simple to solve, just synchronize on the repository and thus enforce a single thread mode. Trivial, dead problem. Unfortunately I don't think that was the scenario that led to deadlocks but I dont' remember as Sacha and Jung were the ones that got it... but if that is the case that is fairly simple to solve... I can't remember and would rather not stay in the uncertain land. Where does the "loadClassInternal()" intervene? marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
