1 Reply Latest reply on Mar 3, 2010 1:39 PM by peterj

    is there an standard way to troubleshoot deployment issue

    hpellan

      Hello,

       

      I have the following trace in server.trace when deploying my service:

       

      ERROR (main) [URLDeploymentScanner] Incomplete Deployment listing:

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@7fc7ae09 { url=file:/var/lib/OC/imsc/server/imsc-1/local-deploy/sipc2c.war }
        deployer: MBeanProxyExt[jboss.web:service=WebServer]
        status: null
        state: CREATE_DEPLOYER
        watch: file:/var/lib/OC/imsc/server/imsc-1/local-deploy/sipc2c.war
        altDD: null
        lastDeployed: 1266427270921
        lastModified: 1266427270000
        mbeans:

      I have enabled the org.jboss log4j traces up to the DEBUG level but that does not tell me anything on what is the issue beyond the above trace (I mean I don't see any classloader error nor any xml file analysis error).

       

      Is there some way to know what is going wrong with this war (which by the way seems to work) ?

      Is there some tools to check a war or ear prior to a deployment ?

       

      I am using JBOSS 4.2.3, but I guess my question makes sense for other JBOSS version as well.

       

      Thanks for your help,

      Herve

        • 1. Re: is there an standard way to troubleshoot deployment issue
          peterj
          What you posted is the deployment report that is printed out after the deployer finishes it's work. As you noticed, this report rarely provide any hints as to what went wrong. There should be an ERROR log message, perhaps with a stack trace, earlier in the console log that would provide more information.