This kind of problem usually means the classes showing the bizarre IllegalAccessError have been loaded twice in 2 classloaders. This was happening consistently with most or all jboss 3.x versions in mid July but should be fixed in all current cvs and released versions. If your JBoss is reasonably up to date check very carefully to see if the classes are in 2 jars.
david jencks On 2002.09.11 16:39:53 -0400 Thomas Osterlie wrote: > Hi, > > I'm setting up a bare bones JBoss JMX server running only the services > required to deploy sar's. It has thus far proven fairly simple, but now > I've come across a problem that puzzles me. > > Running a server configuration called test, if I load the EJBdeployer > mbean from the $JBOSS_ROOT/server/test/conf/jboss-service.xml, the > EJBdeployer works perfectly. Loading the EJBdeployer as an independent > sar (using the same XML-config as previously found in > conf/jboss-service.xml), JBoss is able to load the sar and start the > EJBdeployer without any errors. However, when trying to deploy an EJB I > get the following stack trace: > > org.jboss.deployment.DeploymentException: Could not create deployment: > file:/opt/jboss/test/deploy/interest.jar; - nested throwable: > (java.lang.IllegalAccessError: try to access field > org.jboss.management.j2ee.J2EEServer.sIsActive from class > org.jboss.management.j2ee.EJBModule) > at > org.jboss.deployment.MainDeployer.create(MainDeployer.java:757) > at > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:614) > at > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:581) > 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) > at > >org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) > at > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > at $Proxy4.deploy(Unknown Source) > at > >org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:412) > at > >org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:607) > at > org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:480) > at > >org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:202) > at > >org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:191) > > --- > > Can anyone tell me what the difference is between loading an mbean from > the conf/jboss-service.xml file and as a sar in the deploy dir? When > should a service be added to conf/jboss-service.xml and when can it be > left as an independent sar? > > Cheers, > > Thomas > > > ------------------------------------------------------- > In remembrance > www.osdn.com/911/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
