;
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
>
>
> Robert Cauble wrote:
>
> > If I take jboss 3.2.2 out-of-the-box and rename
> > server/default/deploy/jmx-console.war to ROOT.war and I try going
to
> > t
If I take jboss 3.2.2 out-of-the-box
and rename server/default/deploy/jmx-console.war to ROOT.war and I try going to the url
http://localhost:8080 I
get a “HTTP Status 500 – No Content configured to process this
request” response.
I can then go to http://localhost:8080/ROOT
and it wor
I'm not sure if this is the same thing, but I ran into an issue in axis where it
caches the classloader of the first webapp which calls into axis. I tracked it down to
the method getClassLoaders of AxisProperties.java:
private static ClassLoaders getClassLoaders() {
if (loaders == null)
ircularityError-
> 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:
>
: RE: [JBoss-user] Re:[JBoss-user]ClassCircularityError-
> QueuedPessimisticEJBLock$TxLock
>
> 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
&
> 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 when instances of the same class name
> but different cla
[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-base
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 archi
