http://developer.java.sun.com/developer/bugParade/bugs/4406709.html

I just did a (too harsh?) comment to that closed "non-bug" trying to explain

why that issue is indeed a "showstopper".

FYI: The new JBoss3.0 classloading scheme sometimes has problems with
exactly that behaviour. Since threading
Is involved, this may turn out as a rather non-deterministic and rare thing,
but nevertheless problematic.
 
I have no idea whether these guys have ever reopened a bug after being
bombed with comments?

But lets try: If you feel that this is an important issue (which should be
for everyone that likes the new
and incredibly useful UnifiedClassLoaders) please add a "Me too!" comment or
whatever there.

Maybe you should not mention Jboss to increase the chances of being not
ignored ???

May the source be with you,
CGJ
  

-----Ursprüngliche Nachricht-----
Von: Dave Smith [mailto:[EMAIL PROTECTED]] 
Gesendet: Mittwoch, 10. April 2002 23:22
An: Jung , Dr. Christoph
Betreff: Re: AW: [JBoss-dev] Thread deadlock in class loader


Seems like sun does not think it is a bug

http://developer.java.sun.com/developer/bugParade/bugs/4406709.html

> -----Ursprüngliche Nachricht-----
> Von: Dave Smith [mailto:[EMAIL PROTECTED]]
> Gesendet: Montag, 8. April 2002 17:43
> An: Jboss-Development@Lists. ""Sourceforge. Net
> Betreff: [JBoss-dev] Thread deadlock in class loader
> 
> 
> 
> I have a strange deadlock problem between two threads that are
> completely unrelated. Could some-one point me in the right direction 
> to solve this problem. Here are the two threads in question .. The 
> first one ins accessing thrid party jars and the second one is trying 
> to look up an entity bean and is getting hung up in the jaas security.
> 
> 

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

Reply via email to