1 Reply Latest reply on Jan 6, 2003 4:29 PM by jmc_o_bfd

    problem starting new jboss cluster

    jmc_o_bfd

      Hello all,

      I'm seeing the following error repeatedly when trying to start up the standard "all" configuration for JBoss 3.0.4 with Tomcat 4.1.12, running on Windows XP. At the end of server startup, I get this message:

      14:52:59,714 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.net:service=Axis state: CONFIGURED
      I Depend On: jboss.web:service=JBossWeb
      Depends On Me: jboss.net:service=Adaptor
      , ObjectName: jboss.net:service=Adaptor state: CONFIGURED
      I Depend On: jboss.net:service=Axis
      Depends On Me: , ObjectName: jboss.j2ee:jndiName=jetty/CMPState,service=EJB state: FAILED
      I Depend On:
      Depends On Me: java.lang.ClassNotFoundException: org.mortbay.j2ee.session.interfaces.CMPStateHome]

      This is curious because, as I said, I'm using Tomcat as my servlet container. I don't understand why jboss would then be looking for Jetty classes and interfaces.

      Please let me know if I need to provide more information to help debug this. Thanks in advance,

      jonMC

        • 1. Re: problem starting new jboss cluster
          jmc_o_bfd

          So it looks like the origin of the problem is that the class org.mortbay.j2ee.session.ejb.CMPStateBean references its home interface (org.mortbay.j2ee.session.ejb.interfaces.CMPStateHome), which is not present in the jbossweb-ejb.jar sitting in my deploy directory. This is throwing a ClassNotFoundException when trying to deploy the CMPState EJB. What to do?

          To repeat from the previous post, I am using:
          - JBoss 3.0.4
          - Tomcat 4.1.12 (bundled with JBoss)
          - Windows XP
          without having made any other changes than to add the distributable tag to my webapp's web.xml file. Do I have a bad jbossweb-ejb.jar, or is there another step I should have taken that would prevent the error I'm seeing.

          Help appreciated,

          jonMC