Nevermid the previous reply, I thought your were talking about UnifiedLoaderRepository, not UnifiedLoaderRepository2. The self synchronization of the HeirarchicalLoaderRepository2 does look questionable.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Adrian Brock" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 10:47 AM Subject: RE: [JBoss-dev] [ jboss-Bugs-617574 ] Classloader deadlock > Hello, > > I agree the SCL is not in play here. > > Why does the HeirarchicalLoaderRepository2 synchronize on itself > in loadClass()? A plain UnifiedLoaderRepository2 does not. > > Regards, > Adrian > > >From: "Bordet, Simone" <[EMAIL PROTECTED]> > >Reply-To: [EMAIL PROTECTED] > >To: <[EMAIL PROTECTED]> > >Subject: RE: [JBoss-dev] [ jboss-Bugs-617574 ] Classloader deadlock > >Date: Wed, 2 Oct 2002 19:11:59 +0200 > > > >Hi, > > > > > I come back again with my old trick that hadn't much success > > > in the past. > > > > > > To solve the system class loader problem definitivly, at > > > least with JDK 1.4 > > > and upper, why not use the "java.system.class.loader" system > > > property (see > > > javadoc of java.lang.Classloader.getSystemClassLoader). > > > > > > This way, we could have a "Fake Classloader", let's call it a > > > "RedirectorClassLoader" (RCL), registered as the system > > > classloader. When a > > > call originates from a UCL, the RCL would do its normal work. > > > But when a > > > call doesn't come from a UCL, the RCL would check what is the current > > > "contextual" UCL (as we could/can have multiple UCLs) and delegate the > > > loading to this UCL. > > > >Not sure if your trick works with Class.forName() in all cases, especially > >when to go native is some JDK class such as VersionHelper12. > >Class.forName goes native before calling the classloader, and there it > >acquires the lock on the classloader; then it delegates to the classloader, > >which either is a UCL(2) or a child; from the UCL you walk the hierarchy > >up, arriving to the system classloader (or your RCL), but we already had > >the chance to intercept the call at UCL level. > > > >Maybe I am missing something or I misunderstood your proposal ? > > > >A feeling I have is that it is a plain old bug in HierarchyCL, but it's > >just a feeling (since it does not seem related to the ClassCircularityError > >we had in the past). > > > >Regards, > > > >Simon > > > > > >------------------------------------------------------- > >This sf.net email is sponsored by:ThinkGeek > >Welcome to geek heaven. > >http://thinkgeek.com/sf > >_______________________________________________ > >Jboss-development mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > _________________________________________________________________ > Send and receive Hotmail on your mobile device: http://mobile.msn.com > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
