.
Thanks,
Rob
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-user-
[EMAIL PROTECTED] On Behalf Of Scott M Stark
Sent: Thursday, September 25, 2003 9:14 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Re:[JBoss-user]ClassCircularityError-
QueuedPessimisticEJBLock$TxLock
such that you switched to UnifiedClassLoader3?
Thanks,
Rob
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-user-
[EMAIL PROTECTED] On Behalf Of Adrian Brock
Sent: Wednesday, September 24, 2003 2:05 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Re:[JBoss-user
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-user-
[EMAIL PROTECTED] On Behalf Of Adrian Brock
Sent: Wednesday, September 24, 2003 2:05 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Re:[JBoss-user]ClassCircularityError-
QueuedPessimisticEJBLock$TxLock
Version 2 still suffers from deadlock problems because is does not
reliquish the class loader lock. The only hack to workaround the vm
issue would be to retry loading after seeing a CCE.
Robert Cauble wrote:
Thanks - I really appreciate the help.
Also, is this problem something which you have
Can someone please point me towards some documentation which
describes the advantage of the UnifiedClassLoader
model over the tree-based class loading model? We purchased the JBoss documentation and all it says in the administrators guide
is that JBoss 3.x employs a new class loading
-referencing
it would need to be redeployed anyway.
Thanks,
Rob
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-user-
[EMAIL PROTECTED] On Behalf Of Adrian Brock
Sent: Wednesday, September 24, 2003 9:35 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Re: [JBoss-user
: [JBoss-user] Re: [JBoss-user] ClassCircularityError-
QueuedPessimisticEJBLock$TxLock
On Wed, 2003-09-24 at 14:49, Robert Cauble wrote:
Can someone please point me towards some documentation which
describes
the advantage of the UnifiedClassLoader model over the tree-based
class
On Wed, 2003-09-24 at 19:54, Robert Cauble wrote:
Multiple classloaders is more restrictive when it comes to
the security model. Classes in the same package cannot access
package private methods if the classes are in different classloaders.
Got it. Thanks.
You can also get errors
See bug#4699981, ClassCircularityError thrown without reason
during class loading
http://developer.java.sun.com/developer/bugParade/bugs/4699981.html
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Toshiya Kobayashi wrote:
Hi all,
