3 Replies Latest reply on Mar 14, 2005 4:36 AM by darranl

    Jboss Deployment Error

    aneiba

      Dear All

      Does anyone know what couses the below error?


      12:09:52,280 ERROR [Server] Root deployment has missing dependencies; continuing
      Incomplete Deployment listing:
      Packages waiting for a deployer:
      [org.jboss.deployment.DeploymentInfo@44c724f6 { url=file:/C:/pdaDemo/jboss/server/default/tmp/deploy/server/default/de
      ploy/alphaSerendipity.ear/2.alphaSerendipity.ear-contents/alphaEJB.jar }
      deployer: null
      status: Starting
      state: START_SUBDEPLOYMENTS
      watch: file:/C:/pdaDemo/jboss/server/default/tmp/deploy/server/default/deploy/alphaSerendipity.ear/2.alphaSerendipit
      y.ear-contents/alphaEJB.jar
      lastDeployed: 1110456592050
      lastModified: 1110456591920
      mbeans:
      , org.jboss.deployment.DeploymentInfo@2ccd493a { url=file:/C:/pdaDemo/jboss/server/default/tmp/deploy/server/default/d
      eploy/alphaSerendipity.ear/2.alphaSerendipity.ear-contents/alphaWeb.war }
      deployer: null
      status: Starting
      state: START_SUBDEPLOYMENTS
      watch: file:/C:/pdaDemo/jboss/server/default/tmp/deploy/server/default/deploy/alphaSerendipity.ear/2.alphaSerendipit
      y.ear-contents/alphaWeb.war
      lastDeployed: 1110456592100
      lastModified: 1110456591950
      mbeans:
      ]Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.ejb:service=EJBDeployer
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager
      jboss:service=WebService

      Depends On Me: , ObjectName: jboss:service=invoker,type=jrmp
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager

      Depends On Me: , ObjectName: jboss:service=invoker,type=local
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager

      Depends On Me: , ObjectName: jboss:service=invoker,type=pooled
      state: CONFIGURED
      I Depend On: jboss:service=TransactionManager

      Depends On Me: ]
      at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1152)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
      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:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy6.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:388)
      at java.lang.Thread.run(Thread.java:534)
      12:09:53,722 INFO [Server] JBoss (MX MicroKernel) [3.2.1 (build: CVSTag=JBoss_3_2_1 date=200305041533)] Started in 5s
      :107ms



      Many Thanks,

      Adel

        • 1. Re: Jboss Deployment Error
          darranl

          Can you get JBoss to start cleanly without your ear deployed? It looks as if some of the core services are failing to start.

          • 2. Re: Jboss Deployment Error
            amitbhagat1

            HI, I'm also getting the same problem. If u resolved this problem. Help me 2 :)

            • 3. Re: Jboss Deployment Error
              darranl

              amitbhagat1, If your problem is the same can you please answer the question that I posted.

              Can you get JBoss to start cleanly without your ear deployed?


              That is the issue that needs to be resolved first. There should be some more errors higher up the log that will help to track down the problem.

              Also is there a reason for using an old version of JBoss, have you tried upgrading to 3.2.7?