2 Replies Latest reply on Aug 17, 2006 1:46 PM by sam rogers

    jboss started but not serving

    sam rogers Newbie

      I have tried multiple re-installs, both web and zip, of JBoss AS 4.04. At one point I had it working, but then it stopped. I reinstalled and tested fresh JDK1.5.07. Is there any secret installation path for Windows XP Pro? Any help would be appreciated.
      Thanks,
      Blake

      here is the end portion of jboss server's long run.bat output:

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@3e40275e { url=file:/C:/Program Files/jboss-
      4.0.4.GA/server/default/deploy/tc5-cluster.sar/tc5-cluster.aop }
      deployer: org.jboss.aop.deployment.AspectDeployer@109de5b
      status: Created
      state: CREATED
      watch: file:/C:/Program Files/jboss-4.0.4.GA/server/default/deploy/tc5-cluster
      .sar/tc5-cluster.aop
      altDD: null
      lastDeployed: 1155757701328
      lastModified: 1155757701328
      mbeans:

      org.jboss.deployment.DeploymentInfo@f5abeb7f { url=file:/C:/Program Files/jboss-
      4.0.4.GA/server/default/deploy/tc5-cluster.sar/ }
      deployer: org.jboss.deployment.SARDeployer@153c375
      status: Deployment FAILED reason: org.apache.commons.logging.LogConfigurationE
      xception: No suitable Log constructor [Ljava.lang.Class;@1217e67 for org.apache.
      commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/
      apache/log4j/Category) (Caused by org.apache.commons.logging.LogConfigurationExc
      eption: No suitable Log constructor [Ljava.lang.Class;@1217e67 for org.apache.co
      mmons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/ap
      ache/log4j/Category)); - nested throwable: (org.apache.commons.logging.LogConfig
      urationException: org.apache.commons.logging.LogConfigurationException: No suita
      ble Log constructor [Ljava.lang.Class;@1217e67 for org.apache.commons.logging.im
      pl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Categ
      ory) (Caused by org.apache.commons.logging.LogConfigurationException: No suitabl
      e Log constructor [Ljava.lang.Class;@1217e67 for org.apache.commons.logging.impl
      .Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Categor
      y)))
      state: FAILED
      watch: file:/C:/Program Files/jboss-4.0.4.GA/server/default/deploy/tc5-cluster
      .sar/META-INF/jboss-service.xml
      altDD: null
      lastDeployed: 1155757701328
      lastModified: 1155757648218
      mbeans:

      org.jboss.deployment.DeploymentInfo@2afbbc2f { url=file:/C:/Program Files/jboss-
      4.0.4.GA/server/default/deploy/jmx-console.war/ }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/C:/Program Files/jboss-4.0.4.GA/server/default/deploy/jmx-console
      .war/
      altDD: null
      lastDeployed: 1155757706562
      lastModified: 1155757645171
      mbeans:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.web:service=WebServer
      State: FAILED
      Reason: java.lang.ExceptionInInitializerError
      I Depend On:
      jboss.security:service=JaasSecurityManager
      jboss:service=TransactionManager
      Depends On Me:
      jboss.ws:service=WebServiceDeployerJSE
      jboss.mq:service=InvocationLayer,type=HTTP
      jboss:service=FarmMember,partition=DefaultPartition

      ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=Invoker
      jboss.web:service=WebServer

      ObjectName: jboss:service=DefaultPartition
      State: FAILED
      Reason: java.lang.ExceptionInInitializerError
      I Depend On:
      jboss:service=Naming
      Depends On Me:
      jboss:service=HASessionState
      jboss:service=HAJNDI
      jboss.cache:service=InvalidationBridge,type=JavaGroups
      jboss.ha:service=HASingletonDeployer
      jboss:service=FarmMember,partition=DefaultPartition

      ObjectName: jboss:service=HASessionState
      State: CONFIGURED
      I Depend On:
      jboss:service=Naming
      jboss:service=DefaultPartition

      ObjectName: jboss:service=HAJNDI
      State: CONFIGURED
      I Depend On:
      jboss:service=DefaultPartition
      jboss.system:service=ThreadPool

      ObjectName: jboss.cache:service=InvalidationBridge,type=JavaGroups
      State: CONFIGURED
      I Depend On:
      jboss:service=DefaultPartition
      jboss.cache:service=InvalidationManager

      ObjectName: jboss.ha:service=HASingletonDeployer
      State: CONFIGURED
      I Depend On:
      jboss:service=DefaultPartition
      jboss.system:service=MainDeployer

      ObjectName: jboss:service=FarmMember,partition=DefaultPartition
      State: CONFIGURED
      I Depend On:
      jboss:service=DefaultPartition
      jboss.web:service=WebServer
      jboss.system:service=MainDeployer

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.web:service=WebServer
      State: FAILED
      Reason: java.lang.ExceptionInInitializerError
      I Depend On:
      jboss.security:service=JaasSecurityManager
      jboss:service=TransactionManager
      Depends On Me:
      jboss.ws:service=WebServiceDeployerJSE
      jboss.mq:service=InvocationLayer,type=HTTP
      jboss:service=FarmMember,partition=DefaultPartition

      ObjectName: jboss:service=DefaultPartition
      State: FAILED
      Reason: java.lang.ExceptionInInitializerError
      I Depend On:
      jboss:service=Naming
      Depends On Me:
      jboss:service=HASessionState
      jboss:service=HAJNDI
      jboss.cache:service=InvalidationBridge,type=JavaGroups
      jboss.ha:service=HASingletonDeployer
      jboss:service=FarmMember,partition=DefaultPartition


      12:48:26,687 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBos
      s_4_0_4_GA date=200605151000)] Started in 10s:750ms

        • 1. Re: jboss started but not serving
          Peter Johnson Master

          The root cause is: Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category

          I am going to make the assumption that you installed via the installation jar file, and that you chose to install everything. For some reason, it appears that the log4j.jar file is missing. You could try reinstalling (this time don't select the clustering option, I'm assuming that clustering might have some cause regarding the problem, but that could simply be the poor service that is the first to stumble upon the problem).

          Another option is to ditch the installer, and just download the binary zip file and unzip it to a directory. That's what I did on both Linux and Windows, and have been happily running 4.0.4 for months.

          If you need EJB 3 support, you could use the installer jar to install the basic EJB option (no clustering), or you could download the source and compile it with the 5.0 JDK.

          As a last thought, you could always get a log4j.jar file and place it into the server/default/lib directory.

          • 2. Re: jboss started but not serving
            sam rogers Newbie

            Peter, thanks for your reply. I found the problem - I had installed Java in Program Files. Once I installed both Java and JBoss 4.04GA (from the zip) in directories with no spaces in their names, I had no problem deploying my web app. The default automated installs for both JDK and JBoss target Program Files directory.
            Blake