0 Replies Latest reply on May 13, 2003 2:10 PM by Collin

    3.2.1 Not deploying EJBs

    Collin Novice

      Hi... I just upgraded to 3.2.1 from 3.2RC4, and just got JBoss to start up without throwing any exceptions. However, when I check the jmx-console, I see that none of my beans are deployed, which you can imagine is causing quite a ruckus over here :)

      We deploy our EAR and JAR files as flat files, un-archived. So, our directory structure looks like this:

      << EAR >>
      %deploy%/contentxml.ear/

      << EJBs>>
      %deploy%/contentxml.ear/cxml_ejb.jar/
      %deploy%/contentxml.ear/cxml_ejb.jar/META-INF/
      %deploy%/contentxml.ear/cxml_ejb.jar/META-INF/ejb-jar.xml
      %deploy%/contentxml.ear/cxml_ejb.jar/META-INF/jboss.xml
      %deploy%/contentxml.ear/cxml_ejb.jar/META-INF/jbosscmp-jdbc.xml

      << WARs >>
      %deploy%/contentxml.ear/admin.war/
      ...
      %deploy%/contentxml.ear/publish.war/
      ...

      Now, the WARs themselves deploy just fine, but they can't look up any EJBs because they aren't deployed. In the JMX console, it does have the EAR listed as an application under which the WARs reside. It's not processing the ejb-jar.xml file at all, and I know this because I opened it and made the XML invalid, and JBoss behaved exactly like the previous boot with a valid ejb-jar.xml file.

      In the deployment log, I get this following error about the EAR file:

      14:27:10,035 DEBUG [J2EEApplication] Could not create JSR-77 J2EEApplication: jboss.management.local:J2EEServer=Local,j2eeType=J2EEApplication,name=contentxml.ear
      javax.management.InstanceAlreadyExistsException: jboss.management.local:J2EEServer=Local,j2eeType=J2EEApplication,name=contentxml.ear already registered.
      at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:617)
      at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:198)
      at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
      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.interceptor.ObjectReferenceInterceptor.invoke(ObjectReferenceInterceptor.java:59)
      at org.jboss.mx.interceptor.MBeanAttributeInterceptor.invoke(MBeanAttributeInterceptor.java:43)
      at org.jboss.mx.interceptor.PersistenceInterceptor2.invoke(PersistenceInterceptor2.java:93)
      at org.jboss.mx.server.MBeanInvoker.invoke(MBeanInvoker.java:75)
      at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:141)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:994)
      at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:330)
      at org.jboss.management.j2ee.J2EEApplication.create(J2EEApplication.java:67)
      at org.jboss.management.j2ee.factory.EARModuleFactory.create(EARModuleFactory.java:34)
      at org.jboss.management.j2ee.LocalJBossServerDomain.handleNotification(LocalJBossServerDomain.java:365)
      at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:71)
      at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:82)
      at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java:178)
      at org.jboss.deployment.EARDeployer.start(EARDeployer.java:196)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
      at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)
      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:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy7.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:476)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:200)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:273)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
      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:549)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
      at $Proxy0.start(Unknown Source)
      ......

      I figure that this is why none of the beans are deploying, but I'm not sure. This was the only exception I could find in the boot log.

      Does anyone else have a problem like this? I would really appreciate any help, as I'd like to move to 3.2.1 :)

      thanks-
      Collin