4 Replies Latest reply on Aug 8, 2007 5:53 AM by Gary Ratcliffe

    Configuration Problem - Incompletely deployed packages

    Peter Petermann Newbie

      Hello,
      I installed JBoss on my Windows 2003 Server machine with SP2 according to the installation Guide, but i get allway this error, if i try to start JBoss:

      15:51:59, 156 ERROR [URLDeploymentscanner] Incomplete Deployment listing:

      --- Packages waiting for a deployer ---
      org.jboss.deployment.DeploymentInfo@1d564b40 { url=file:/D:/jboss/server/all/dep loy/adobe-ds-jboss-mysql.xml }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/D:/jboss/server/all/deploy/adobe-ds-jboss-mysql.xml
      altDD: null
      lastDeployed: 1186494719156
      lastModified: 1186494719156
      mbeans:

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@1d564b40 { url=file:/D:/jboss/server/all/dep loy/adobe-ds-jboss-mysql.xml }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/D:/jboss/server/all/deploy/adobe-ds-jboss-mysql.xml
      altDD: null
      lastDeployed: 1186494719156
      lastModified: 1186494719156
      mbeans:


      therefore i cann't start JBoss

      what i have done wrong??

      can anyone help me to solve this problem?

      Thankyou

        • 1. Re: Configuration Problem - Incompletely deployed packages
          Gary Ratcliffe Newbie

          The file that is not being deployed, adobe-ds-jboss-mysql.xml, does not following the naming convention of any installed deployer within JBoss. For example -service.xml. From the name of the file I suspect this is a DataSource definition. The registered extension for this is -ds.xml.

          So if you rename adobe-ds-jboss-mysql.xml to adobe-jboss-mysql-ds.xml it will attempt to deployer it as a DataSource.

          Gary

          • 2. Re: Configuration Problem - Incompletely deployed packages
            Peter Petermann Newbie

            You are right. this is a DataSource.
            After renaming the file the JBoss still stopping by

            D:\jboss\bin>run.bat -c all
            ===============================================================================
            .
            JBoss Bootstrap Environment
            .
            JBOSS_HOME: D:\jboss\bin\\..
            .
            JAVA: C:\Programme\Java\jdk1.6.0\bin\java
            .
            JAVA_OPTS: -Dadobeidp.serverName=server1 -DCASBOOTPROPS=bam.properties -Dcom.
            celequest.bootstrap.envpropname=CASBOOTPROPS -Dfile.encoding=utf8 -Djava.net.pre
            ferIPv4Stack=true -Dprogram.name=run.bat -Djava.security.manager -Djava.security
            .policy=../server/all/conf/server.policy -Djava.security.debug=failure -XX:MaxPe
            rmSize=256m -Xms256m -Xmx1024m
            .
            CLASSPATH: C:\Programme\Java\jdk1.6.0\lib\tools.jar;D:\jboss\bin\\run.jar
            .
            ===============================================================================
            .
            15:51:41,812 INFO [Server] Starting JBoss (MX MicroKernel)...
            15:51:41,812 INFO [Server] Release ID: JBoss [Zion] 4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)
            15:51:41,812 INFO [Server] Home Dir: D:\jboss
            15:51:41,812 INFO [Server] Home URL: file:/D:/jboss/
            15:51:41,812 INFO [Server] Patch URL: null
            15:51:41,812 INFO [Server] Server Name: all
            15:51:41,812 INFO [Server] Server Home Dir: D:\jboss\server\all
            15:51:41,812 INFO [Server] Server Home URL: file:/D:/jboss/server/all/
            15:51:41,812 INFO [Server] Server Temp Dir: D:\jboss\server\all\tmp
            15:51:41,828 INFO [Server] Root Deployment Filename: jboss-service.xml
            15:51:42,093 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
            15:51:42,093 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
            15:51:42,093 INFO [ServerInfo] OS-System: Windows 2003 5.2,x86
            15:51:42,453 INFO [Server] Core system initialized
            15:51:44,515 INFO [WebService] Using RMI server codebase: http://TOXSERVER2:8083/
            15:51:44,531 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml

            • 3. Re: Configuration Problem - Incompletely deployed packages
              Peter Johnson Master

              The 'all' configuration assumes that it will be clustered with multiple app servers. As such, it requires more from your network than a non-clustered configuration. I recommend that you try the 'default' configuration first.

              • 4. Re: Configuration Problem - Incompletely deployed packages
                Gary Ratcliffe Newbie

                OK, You seem to have got further.

                I'm not sure what you mean by 'After renaming the file the JBoss still stopping by'. Are you saying that there are still errors during startup?

                Something you may also wish to check is that the name of your data source file suggests its is MySQL. You need to make sure the JDBC driver jar file for MySQL can be accessed by copying the jar files into server/all/lib or ensuring it is on the classpath before JBoss is started.

                Gary