1 Reply Latest reply on Oct 22, 2002 2:26 PM by adrian.brock

    jdom.jar in server/default/lib -> ERROR [URLDeploymentScanne

    guze

      Deploying jdom.jar in server/default/lib causes

      23:43:21,422 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:
      [org.jboss.deployment.DeploymentInfo@7777caae { url=file:/opt/jboss-3.0.3/server/default/lib/jdom.jar }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/opt/jboss-3.0.3/server/default/lib/jdom.jar
      lastDeployed: 1035236590189
      lastModified: 1035236551000
      mbeans:
      ]Incompletely deployed packages:
      :

      during/after server startup.

      Seems, there are no negative effects (no malfunctions in ejbs and mbeans depending on jdom.jar).

      Workaround: jdom.jar in $JBOSS_HOME/lib and run.sh -L jdom.jar

        • 1. Re: jdom.jar in server/default/lib -> ERROR [URLDeploymentSc

          The jdom.jar is deployed as a normal classes jar.
          This is the first step in deployment.

          Before a deployer is determined, the classes are
          available to the system.

          The message relates to the MainDeployer waiting
          for something that understands META-INF/info.xml
          to complete the deployment, which obviously never
          happens.

          Regards,
          Adrian