6 Replies Latest reply on Oct 27, 2008 11:35 AM by Kevin Taute

    Incomplete Deployment Listing Error in JBoss 4.0.4

    somu junkee Newbie

      I get this error in stand-alone as well as three node JBoss 4.0.4 clustered environment when I try to deploy the application (without webservices).

      [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing

      But when I delete jbossws14.sar, I can deploy the application successfully.

      Should I include the webservices jbossws14.sar file only if I use webservices in my aplication and delete it for non web services applications? Any help on this is appreciated.

      Thanks

        • 1. Re: Incomplete Deployment Listing Error in JBoss 4.0.4
          Thomas Diesler Master

          Generally, you should remove any services that are not needed so they want consume resources.

          Is there any relevant stack trace for me to look at?

          • 2. Incomplete Deployment Listing Error in JBoss
            Hanumanth Reddy Newbie

            ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

            --- Packages waiting for a deployer ---
            org.jboss.deployment.DeploymentInfo@b7c8952 { url=file:/C:/Prox/apps/JBoss/server/default/deploy/reports/GOActivationPatronsActivatedReport.jrxml }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/C:/Prox/apps/JBoss/server/default/deploy/reports/GOActivationPatronsActivatedReport.jrxml
            altDD: null
            lastDeployed: 1216277423703
            lastModified: 1216277423703
            mbeans:

            org.jboss.deployment.DeploymentInfo@47786940 { url=file:/C:/Prox/apps/JBoss/server/default/deploy/reports/GOActivationPrepaidByStation.jrxml }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/C:/Prox/apps/JBoss/server/default/deploy/reports/GOActivationPrepaidByStation.jrxml
            altDD: null
            lastDeployed: 1216277423703
            lastModified: 1216277423703
            mbeans:

            org.jboss.deployment.DeploymentInfo@33964fc6 { url=file:/C:/Prox/apps/JBoss/server/default/deploy/reports/GOActivationReport.jrxml }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/C:/Prox/apps/JBoss/server/default/deploy/reports/GOActivationReport.jrxml
            altDD: null
            lastDeployed: 1216277423718
            lastModified: 1216277423703
            mbeans:

            • 3. Re: Incomplete Deployment Listing Error in JBoss 4.0.4
              Peter Johnson Master

              What is a jrxml file? The error message is stating that there is no deployer that knows how to deploy jrxml file.

              What is the "reports" directory?

              • 4. Re: Incomplete Deployment Listing Error in JBoss 4.0.4
                Kevin Taute Newbie

                jrxml is a Jasper Reports definition file. It looks like he is trying to deploy an application that includes reports (reports directory) from jasper reports.

                There is a free reporting tool called iReports that generates the jrxml files, and includes the required jar files for utilizing Jasper reports in a production environment.

                I haven't used Jasper and/or iReports with Jboss in the last few years, so I can't really help with the problem :(

                • 5. Re: Incomplete Deployment Listing Error in JBoss 4.0.4
                  Peter Johnson Master

                  Looks like the reports need to be written elsewhere - they should not be in the deploy directory nor in one of its subdirectories.

                  • 6. Re: Incomplete Deployment Listing Error in JBoss 4.0.4
                    Kevin Taute Newbie

                    The Jasper Reports API requires access to the text file definition (jrxml). In order to deploy under jboss, you will need to include the jrxml file like any other text file being deployed (ie your html, jsp, etc), then use something like

                    String dirName = getServletContext().getRealPath("/");


                    to get the root directory of your application. If you chose to place them in a subfolder (such as reports) you would need to add that to the string above.