As a quick work-around while I�m busy today with doing business (buaaeeeh:-(
Patch the java.lang.ClassLoader class ... Either remove the synchronized keyword from loadClassInternal (should be safe) or make it protected and remove the synchronized keyword in an overriding method of UnifiedClassLoader (makes the build Depending on that patch, not that nice). Put the patched class in a patch.jar and start jboss With the option -Xbootclasspath/a:patch.jar Viola, CGJ -----Urspr�ngliche Nachricht----- Von: marc fleury [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 22. April 2002 20:04 An: Jboss-Development@Lists. Sourceforge. Net Cc: Christoph Jung; sacha labourey Betreff: Workaround for CL stuff 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
