Do you see this when building from Branch_3_0 too? --jason
Quoting Andreas Schaefer <[EMAIL PROTECTED]>: > Hi Geeks > > Currently I get this exceptions on my W2K box when I run it under > Cygwin. DOS Command prompt seems doing fine (both on current > CVS Head). > > Andy > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: "Sacha Labourey" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Thursday, May 09, 2002 10:52 PM > Subject: RE: [JBoss-dev] HEAD & ClassCircularityError > > > > I have not yet tried removing deployments... but I just tried under rc3 > and I > > don't get this exception. I am running the testsuite now to see if that > will > > induce it, but I think I would have seen it by now. > > > > Weird. > > > > --jason > > > > > > Quoting Sacha Labourey <[EMAIL PROTECTED]>: > > > > > Hello Jason, > > > > > > This seems to happen only with Sun JVM on Linux (or some combination of > > > os/jvm/hotspot). I've tried to reproduce this on my jdk 1.3.1, 1.4 on > windows > > > 2000 and have been unable to do so. > > > > > > I've searched sun.com, google, ... and one of the possibilities is that > a JAR > > > that is loaded by JBoss contains some class definitions that are not > > > compatible by the one used by javagroups. Maybe this is even worst with > our > > > own classloader where mixes of definitions can happen more easily. > > > > > > Jason, can you try to remove almost everything from deploy and > > > jboss-services.xml and only deploy the clustering service to see what > > > happen? > > > > > > Cheers, > > > > > > > > > > > Sacha > > > > > > > > > > > > > -----Message d'origine----- > > > > De : [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED]]De la part de > > > > Jason Dillon > > > > Envoy� : jeudi, 9 mai 2002 10:29 > > > > � : [EMAIL PROTECTED]; [EMAIL PROTECTED] > > > > Cc : [EMAIL PROTECTED] > > > > Objet : [JBoss-dev] HEAD & ClassCircularityError > > > > > > > > > > > > From the VM spec 5.3.5 Deriving a Class from a class File > Representation: > > > > ... > > > > * Otherwise, if any of the superclasses of C is C itself, loading > throws > > > a > > > > ClassCircularityError. > > > > ... > > > > * Otherwise, if any of the superinterfaces of C is C itself, > > > > loading throws a > > > > ClassCircularityError. > > > > > > > > Here is a link to the page I looked at: > > > > http://java.sun.com/docs/books/vmspec/2nd-edition/html/ConstantPoo > > > > l.doc.html > > > > > > > > From the Language Spec, here 13.4.4 Superclasses and Superinterfaces: > > > > > > > > A ClassCircularityError is thrown at load time if a class would > > > > be a superclass > > > > of itself. Changes to the class hierarchy that could result in such a > > > > circularity when newly compiled binaries are loaded with > > > > pre-existing binaries > > > > are not recommended for widely distributed classes. > > > > > > > > Taken from: > > > > http://java.sun.com/docs/books/jls/first_edition/html/13.doc.html > > > > > > > > From 12.2.1: > > > > > > > > # ClassCircularityError: A class or interface could not be loaded > > > > because it > > > > would be its own superclass or superinterface > > > > > > > > Why they didn't just put this in the javadocs I have no clue. > > > > > > > > * * * > > > > > > > > I am still getting these very reliably when attempting to deploy > > > > cluster-service.xml. I am running this on Linux under 1.4 and I > > > > also see it > > > > under 1.3.1_03. Here is the first (of many + evil > printStackTrace's): > > > > > > > > <snip> > > > > ChannelException: JChannel(): java.lang.ClassCircularityError: > > > > org/javagroups/log/Trace > > > > at org.javagroups.JChannel.<init>(JChannel.java:144) > > > > at > > > > org.jboss.ha.framework.server.ClusterPartition.createService(Clust > > > > erPartition.java:154) > > > > at > > > > > org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:170) > > > > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > > > > cessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > > at > > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > > > > BeanDispatcher.java:284) > > > > at > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > > > at > > > > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceCont > > > > roller.java:867) > > > > at $Proxy0.create(Unknown Source) > > > > at > > > > org.jboss.system.ServiceController.create(ServiceController.java:271) > > > > at > > > > org.jboss.system.ServiceController.create(ServiceController.java:211) > > > > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > > > > cessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > > at > > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > > > > BeanDispatcher.java:284) > > > > at > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > > > at $Proxy3.create(Unknown Source) > > > > at org.jboss.deployment.SARDeployer.create(SARDeployer.java:277) > > > > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:651) > > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:526) > > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:490) > > > > at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source) > > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > > > > cessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > > at > > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > > > > BeanDispatcher.java:284) > > > > at > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > > > at $Proxy4.deploy(Unknown Source) > > > > at > > > > org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploy > > > > mentScanner.java:405) > > > > at > > > > org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(UR > > > > LDeploymentScanner.java:586) > > > > at > > > > org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeployme > > > > ntScanner.java:465) > > > > at > > > > org.jboss.deployment.scanner.AbstractDeploymentScanner.startServic > > > > e(AbstractDeploymentScanner.java:237) > > > > at > > > > > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:198) > > > > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > > > > cessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > > at > > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > > > > BeanDispatcher.java:284) > > > > at > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > > > at > > > > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceCont > > > > roller.java:867) > > > > at $Proxy0.start(Unknown Source) > > > > at > > > > org.jboss.system.ServiceController.start(ServiceController.java:339) > > > > at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) > > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > > > > cessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > > at > > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > > > > BeanDispatcher.java:284) > > > > at > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > > > at $Proxy3.start(Unknown Source) > > > > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:342) > > > > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:692) > > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:527) > > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:490) > > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:472) > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > at > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm > > > > pl.java:39) > > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > > > > cessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > > at > > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > > > > BeanDispatcher.java:284) > > > > at > > > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > > > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:318) > > > > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216) > > > > at org.jboss.Main.boot(Main.java:148) > > > > at org.jboss.Main$1.run(Main.java:381) > > > > at java.lang.Thread.run(Thread.java:536) > > > > </snip> > > > > > > > > > > > > Is this problem unique to my environment or does anyone else see > > > > this with HEAD? > > > > > > > > --jason > > > > > > > > ------------------------------------------------- > > > > This mail sent through IMP: http://horde.org/imp/ > > > > > > > > _______________________________________________________________ > > > > > > > > Have big pipes? SourceForge.net is looking for download mirrors. We > > > supply > > > > the hardware. You get the recognition. Email Us: > > > [EMAIL PROTECTED] > > > > _______________________________________________ > > > > Jboss-development mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > > > > > > > > ------------------------------------------------- > > This mail sent through IMP: http://horde.org/imp/ > > > > _______________________________________________________________ > > > > Have big pipes? SourceForge.net is looking for download mirrors. We > supply > > the hardware. You get the recognition. Email Us: > [EMAIL PROTECTED] > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
