You can get an incorrect ClassCircularityError during
The bug has been reported to Sun, and they have
accepted it as a bug.
i searched the bug database on http://developer.java.sun.com/developer/bugParade/index.jshtml but could not find the bug
Do you know if it applies to all platforms? I am running Mac OS X with HotSpot 1.3.1, so jrocket is no alternative in this case.
Maybe you could give the bug id.
So what do you recommend? Is the problem fixed in 1.4?
If we are using a HotSpot VM would we be better off sticking to 2.4?
The problem is not fixed in 1.4
People are working on code to workaround the VM bug.
Hopefully, this should make it into 3.0.1
How likely am I to run into this bug? For example, can I avoid it by not asking JBoss to load multiple .ear's at once? Is there some other work-around?
We r also receiving the same err!(SO WHAT?)
Is there any alternative to JROCKIT ?
What is the exact reason for this error.
Well i have one mor question:
IS THERE ANY ADMIN CONSOLE/IDE for JBOSS+TOMCAT ?
Thanks in advance!
Let there be no error anywhere!!
POPNET INFOTECH INDIA LTD.(www.popnet.co.in)
As a follow up to this thread. I was getting the ClassCircularityError while running jboss 3.0 on a Sun E450 with 4 cpu's using Sun's JVM 1.4.0_01 - BEA's Jrockit was not an option as it is not available for Solaris Sparc. I upgraded to Sun JVM 1.4.1-beta1 and this problem appears to have been resolved.
I have just had a look at the release notes
for Jboss 3.0.1 and nomention of work arounds for the
JVM classcircularity error does this mean the work arounds did not make it into 3.0.1?
It is in the changes between 3_0_1RC1 and 3_0_0
"The default class loading mechanism has been changed to a delegation model to
avoid sporadic problems seen with multi-threaded class loading. One typical
problem seen with HotSpot were ClassCircularityErrors."
I encountered this ClassCircularityError loading an org.apache.xpath.* class that was probably also loaded by the core JBoss product somewhere.
It happened erratically depending on where I put my classes -- sometimes it was fatal while other times it was just an error on the console that caused no trouble. One machine didn't have the problem at all.
I installed the jdk1.4.1 beta and the problem went away.
We are running on Win2k boxes.