RE: [JBoss-dev] HEAD ClassCircularityError
Ilike to - then time says - hepp- like - i do have the time to read and grep the 'thingo' - just wait and someboby will force in ! ... You meant blue-sky in an elevator? Whatever -- I know Zahid Rahman. 2002. ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
hi, I know Zahid Rahman. 2002. now THAT should be on the next edition of the jboss t-shirts 8) sorry for the noise, christian ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
well, well, well... (what was the JVM BTW?) Houston, we have a problem. As I told Marc, maybe we have a problem with our classloader in multithreaded situations when two threads are trying to load the same class at the same time and it is not yet cached. If both of these classes have the same mother class (or some equivalent scenario), then the JVM may complain about it. I have not yet found time to do test code for this. Jason, do you know if this occurs with the Blackdown JVM? If it does, we could then take a look at the code of the JVM (or ask the Blackdown guys for some hints) Cheers, Sacha -Message d'origine- De : Jason Dillon [mailto:[EMAIL PROTECTED]] Envoyé : mercredi, 15 mai 2002 02:24 À : Sacha Labourey; [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc : [EMAIL PROTECTED] Objet : Re: [JBoss-dev] HEAD ClassCircularityError And now these, after I recompiled everything from scratch: snip 2002-05-14 17:22:52,321 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackException, causedBy: java.lang.ClassCircularityError: sun/reflect/MethodAccessorImpl at sun.misc.Unsafe.defineClass(Native Method) at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator. java:381) at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerat or.java:377) at sun.reflect.MethodAccessorGenerator.generateMethod(MethodAccessorG enerator.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm pl.java:28) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc cessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(M essageDrivenContainer.java:394) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.i nvoke(CachedConnectionInterceptor.java:147) at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(Mess ageDrivenInstanceInterceptor.java:88) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxI nterceptor.java:87) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInter ceptorCMT.java:165) at ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
jason, sacha or dain i need a test case, and in fact it should be in test cvs have 20 classes (from Class1 to Class20) with impossible links to each other like class1-2, 4, 5 ,8 class8- loops back to one, 4, 9 etc and then 20 threads that each loads a class, if you can package in different packages for several tests our class loaders are the most advanced in the industry and I want to make sure we take care of all cases, marcf PS: be careful last time I chased a CCE error, it would show up under SUN as cce and when I switched to IBM it was something else which made sense and I then fixed (back this summer). A test case would really be great. |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Sacha |Labourey |Sent: Wednesday, May 15, 2002 12:12 AM |To: Jason Dillon; Sacha Labourey; [EMAIL PROTECTED]; [EMAIL PROTECTED] |Cc: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] HEAD ClassCircularityError | | |well, well, well... (what was the JVM BTW?) | |Houston, we have a problem. | |As I told Marc, maybe we have a problem with our classloader in |multithreaded situations when two threads are trying to load the same class |at the same time and it is not yet cached. If both of these |classes have the |same mother class (or some equivalent scenario), then the JVM may complain |about it. I have not yet found time to do test code for this. | |Jason, do you know if this occurs with the Blackdown JVM? If it does, we |could then take a look at the code of the JVM (or ask the |Blackdown guys for |some hints) | |Cheers, | | | Sacha | | | -Message d'origine- | De : Jason Dillon [mailto:[EMAIL PROTECTED]] | Envoyé : mercredi, 15 mai 2002 02:24 | À : Sacha Labourey; [EMAIL PROTECTED]; [EMAIL PROTECTED] | Cc : [EMAIL PROTECTED] | Objet : Re: [JBoss-dev] HEAD ClassCircularityError | | | And now these, after I recompiled everything from scratch: | | snip | 2002-05-14 17:22:52,321 ERROR [org.jboss.ejb.plugins.LogInterceptor] | TransactionRolledbackException, causedBy: | java.lang.ClassCircularityError: sun/reflect/MethodAccessorImpl | at sun.misc.Unsafe.defineClass(Native Method) | at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) | at | sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator. | java:381) | at java.security.AccessController.doPrivileged(Native Method) | at | sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerat | or.java:377) | at | sun.reflect.MethodAccessorGenerator.generateMethod(MethodAccessorG | enerator.java:59) | at | sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm | pl.java:28) | at | sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc | cessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at | org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(M | essageDrivenContainer.java:394) | at | org.jboss.resource.connectionmanager.CachedConnectionInterceptor.i | nvoke(CachedConnectionInterceptor.java:147) | at | org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(Mess | ageDrivenInstanceInterceptor.java:88) | at | org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxI | nterceptor.java:87) | at | org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInter | ceptorCMT.java:165) | at | | |___ | |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 ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
jason, sacha or dain i need a test case, and in fact it should be in test cvs Sure. I don't have time now though. Any one else? Cheers, Sacha ___ 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
Re: [JBoss-dev] HEAD ClassCircularityError
I have seen this mostly on SUN's 1.4 on Linux. I have not touched blackdown since 1.1.7. --jason On Wednesday 15 May 2002 07:11 am, Sacha Labourey wrote: well, well, well... (what was the JVM BTW?) Houston, we have a problem. As I told Marc, maybe we have a problem with our classloader in multithreaded situations when two threads are trying to load the same class at the same time and it is not yet cached. If both of these classes have the same mother class (or some equivalent scenario), then the JVM may complain about it. I have not yet found time to do test code for this. Jason, do you know if this occurs with the Blackdown JVM? If it does, we could then take a look at the code of the JVM (or ask the Blackdown guys for some hints) Cheers, Sacha -Message d'origine- De : Jason Dillon [mailto:[EMAIL PROTECTED]] Envoyé : mercredi, 15 mai 2002 02:24 À : Sacha Labourey; [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc : [EMAIL PROTECTED] Objet : Re: [JBoss-dev] HEAD ClassCircularityError And now these, after I recompiled everything from scratch: snip 2002-05-14 17:22:52,321 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackException, causedBy: java.lang.ClassCircularityError: sun/reflect/MethodAccessorImpl at sun.misc.Unsafe.defineClass(Native Method) at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator. java:381) at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerat or.java:377) at sun.reflect.MethodAccessorGenerator.generateMethod(MethodAccessorG enerator.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm pl.java:28) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc cessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(M essageDrivenContainer.java:394) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.i nvoke(CachedConnectionInterceptor.java:147) at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(Mess ageDrivenInstanceInterceptor.java:88) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxI nterceptor.java:87) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInter ceptorCMT.java:165) at ___ 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
Re: [JBoss-dev] HEAD ClassCircularityError
on 15-05-2 16.51, Sacha Labourey at [EMAIL PROTECTED] wrote: jason, sacha or dain i need a test case, and in fact it should be in test cvs Sure. I don't have time now though. Any one else? Ilike to - then time says - hepp- like - i do have the time to read and grep the 'thingo' - just wait and someboby will force in ! ... Love pf ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Fagerlund Sent: Wednesday, May 15, 2002 7:31 PM To: Sacha Labourey; marc fleury; Jason Dillon; [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] HEAD ClassCircularityError on 15-05-2 16.51, Sacha Labourey at [EMAIL PROTECTED] wrote: jason, sacha or dain i need a test case, and in fact it should be in test cvs Sure. I don't have time now though. Any one else? Ilike to - then time says - hepp- like - i do have the time to read and grep the 'thingo' - just wait and someboby will force in ! ... Love pf Dude are you on crack? ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
| Love | pf | | |Dude are you on crack? | | |___ | |Have big pipes? SourceForge.net is looking for mirrors. We supply I couldn't resist, the sourceforge line (oops pun intended) was just too good ___ 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
Fwd: Re: [JBoss-dev] HEAD ClassCircularityError
Resending due to my messed up sendmail config... -- Forwarded Message -- Subject: Re: [JBoss-dev] HEAD ClassCircularityError Date: Wed, 15 May 2002 00:16:57 + From: Jason Dillon [EMAIL PROTECTED] To: Sacha Labourey [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] I just ran into another CCE in a seperate/non-clustering location. Below is the start of the exception throw when deployed a .ear: snip 17:13:23,440 ERROR [MainDeployer] could not create deployment: njar:file:/home/jason/ws/jboss/jboss-all/build/output/jboss-3.1.0alpha/server /ben/tmp/deploy/server/ben/deploy/manager.ear/81.manager.ear^/mailing.jar java.lang.ClassCircularityError: org/jboss/resource/connectionmanager/PoolFiller at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnect ion(InternalManagedConnectionPool.java:107) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getC onnection(JBossManagedConnectionPool.java:312) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnect ion(BaseConnectionManager2.java:440) at org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConne ction(LocalTxConnectionManager.java:221) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnectio n(BaseConnectionManager2.java:504) at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalData Source.java:101) at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.getConnection(JDBCCommand.java:69 4) at org.jboss.ejb.plugins.jaws.jdbc.JDBCInitCommand.execute(JDBCInitCommand.java: 120) at org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.create(JAWSPersistenceManag er.java:129) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java :155) at org.jboss.ejb.EntityContainer.createService(EntityContainer.java:318) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:170) at org.jboss.ejb.Container.invoke(Container.java:778) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1024) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java :867) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:271) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:25) at java.lang.reflect.Method.invoke(Method.java:324) /snip --jason On Thursday 09 May 2002 08:45 am, Sacha Labourey wrote: 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
Fwd: Re: [JBoss-dev] HEAD ClassCircularityError
Resending due to my messed up sendmail config... -- Forwarded Message -- Subject: Re: [JBoss-dev] HEAD ClassCircularityError Date: Wed, 15 May 2002 00:24:22 + From: Jason Dillon [EMAIL PROTECTED] To: Sacha Labourey [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] And now these, after I recompiled everything from scratch: snip 2002-05-14 17:22:52,321 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackException, causedBy: java.lang.ClassCircularityError: sun/reflect/MethodAccessorImpl at sun.misc.Unsafe.defineClass(Native Method) at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377 ) at sun.reflect.MethodAccessorGenerator.generateMethod(MethodAccessorGenerator.ja va:59) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:28) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrive nContainer.java:394) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(Cache dConnectionInterceptor.java:147) at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenIn stanceInterceptor.java:88) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor. java:87) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.j ava:165) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:51) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:129 ) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinder Interceptor.java:145) at org.jboss.ejb.MessageDrivenContainer.invoke(MessageDrivenContainer.java:311) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java :640) at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(J MSContainerInvoker.java:988) at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:234) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsu mer.java:560) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:377) at org.jboss.mq.SpySession.run(SpySession.java:220) at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:173) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.jav a:655) at java.lang.Thread.run(Thread.java:536) /snip On Thursday 09 May 2002 08:45 am, Sacha Labourey wrote: 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
RE: [JBoss-dev] HEAD ClassCircularityError
Hello Andreas and Bela, I have been able to reproduce the bug with sh from cygwin... very strange! I have compiled a new version from JavaGroups 2.0 and tried: I no more see the problem. Can you check with your environment that was causing the problem? I will send you the jar privately as it is quite big. If it doesn't happen any more, we will commit this new version. Bela, do you know if HEAD of JG2.0 is stable? If this CircularClassException is solved by this new JAR, we will most probably use it. Thank you! Cheers, Sacha -Message d'origine- De : Andreas Schaefer [mailto:[EMAIL PROTECTED]] Envoyé : dimanche, 12 mai 2002 03:11 À : Sacha Labourey; Jason Dillon Cc : [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Objet : Re: [JBoss-dev] HEAD ClassCircularityError Hi Geeks Andreas, on which VM can you see the problem under Windows 2000? Jdk 1.3.1-b24. Note that this problem only occurs under Cygwin Unix shell emulator !! Andy ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
Hey, I did see this problem a few times when running the testsuite... I think it showed up for some cts tests, but I can not reproduce that very well. Perhaps the new jg jar will fix this, but I fear the problem is bigger than that... and harder to track down. I hope that is not the case. --jason Quoting Sacha Labourey [EMAIL PROTECTED]: Hello Andreas and Bela, I have been able to reproduce the bug with sh from cygwin... very strange! I have compiled a new version from JavaGroups 2.0 and tried: I no more see the problem. Can you check with your environment that was causing the problem? I will send you the jar privately as it is quite big. If it doesn't happen any more, we will commit this new version. Bela, do you know if HEAD of JG2.0 is stable? If this CircularClassException is solved by this new JAR, we will most probably use it. Thank you! Cheers, Sacha -Message d'origine- De : Andreas Schaefer [mailto:[EMAIL PROTECTED]] Envoyé : dimanche, 12 mai 2002 03:11 À : Sacha Labourey; Jason Dillon Cc : [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Objet : Re: [JBoss-dev] HEAD ClassCircularityError Hi Geeks Andreas, on which VM can you see the problem under Windows 2000? Jdk 1.3.1-b24. Note that this problem only occurs under Cygwin Unix shell emulator !! Andy ___ 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
RE: [JBoss-dev] HEAD ClassCircularityError
Jason, Ic. Then it appears there is a bug in HEAD which causing these failures. Any ideas what it might be? Is there a web or gui based diff which can show me all of the changes from branch to branch? If not someone want to write one hehe? If you take a look at the recent tests, the circularity error seems to occur with some VM only, maybe there is a link here. Andreas, on which VM can you see the problem under Windows 2000? Jason, here the files that differ between HEAD and Branch_3_0 (in attach). That's strange. We have to deploy the minimal set of services + clustering to see with which JAR (and then class), the problem occurs (I haven't been able to see it yet!). Cheers, Sacha Report.zip Description: Zip compressed data
Re: [JBoss-dev] HEAD ClassCircularityError
Hi Geeks Andreas, on which VM can you see the problem under Windows 2000? Jdk 1.3.1-b24. Note that this problem only occurs under Cygwin Unix shell emulator !! Andy ___ 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
Re: [JBoss-dev] HEAD ClassCircularityError
Hi Geeks No, it seems under Branch 3.0 it works fine under W2K. Andy - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: Andreas Schaefer [EMAIL PROTECTED] Cc: Sacha Labourey [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, May 09, 2002 11:09 PM Subject: Re: [JBoss-dev] HEAD ClassCircularityError 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
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
Re: [JBoss-dev] HEAD ClassCircularityError
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
Re: [JBoss-dev] HEAD ClassCircularityError
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
