4 Replies Latest reply on Aug 28, 2013 1:56 AM by Stephen Coy

    Failed to process jboss-app.xml

    Calvin Kodian Newbie

      While I try to deploy my app to JbossEap 6.1 I get the below error

       

      Content of my jboss-app.xml

      <jboss-app>

      <module-order>strict</module-order>

      </jboss-app>

       

      09:38:09,792 WARN  [org.jboss.metadata.parser.jboss.JBossAppMetaDataParser] (MSC service thread 1-14) module-order element in jboss-app.xml is deprecated and has been ignored

      09:38:09,797 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC000001: Failed to start service jboss.deployment.unit."App.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."App.ear".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "App.ear"

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_51]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_51]

        at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_51]

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011059: Failed to parse "/Users/calvin/apps/jboss-eap-6.1/standalone/deployments/App.ear/META-INF/jboss-app.xml"

        at org.jboss.as.ee.structure.EarMetaDataParsingProcessor.handleJbossMetadata(EarMetaDataParsingProcessor.java:127)

        at org.jboss.as.ee.structure.EarMetaDataParsingProcessor.deploy(EarMetaDataParsingProcessor.java:67)

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        ... 5 more

      Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag().

      at [row,col {unknown-source}]: [2,20]

        at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:606)

        at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:479)

        at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:464)

        at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1169)

        at org.jboss.metadata.parser.jboss.JBossAppMetaDataParser.parse(JBossAppMetaDataParser.java:95)

        at org.jboss.as.ee.structure.EarMetaDataParsingProcessor.handleJbossMetadata(EarMetaDataParsingProcessor.java:124)

        ... 7 more

        • 1. Re: Failed to process jboss-app.xml
          jaikiran pai Master

          Calvin Kodian wrote:

           

          While I try to deploy my app to JbossEap 6.1 I get the below error

           

          Content of my jboss-app.xml

          <jboss-app>

          <module-order>strict</module-order>

          </jboss-app>

           

          The XSD for jboss-app.xml has changed and it no longer supports that module-order element https://github.com/wildfly/wildfly/blob/7.2.0.Final/build/src/main/resources/docs/schema/jboss-app_7_0.xsd. Removing that jboss-app.xml from your application should get you past it.

          1 of 1 people found this helpful
          • 2. Re: Failed to process jboss-app.xml
            Stephen Coy Master

            In addition to what jaikiran pai says, you should update your application.xml to use the

                  <application xmlns="http://java.sun.com/xml/ns/javaee"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
                  http://java.sun.com/xml/ns/javaee/application_6.xsd"
                  version="6">
            

            schema and add the

            <initialize-in-order>true</initialize-in-order>
            

            element.

            1 of 1 people found this helpful
            • 3. Re: Failed to process jboss-app.xml
              Calvin Kodian Newbie

              I got passed that level however I am getting a new error now.

               

              In fact this app runs without any issues in Jboss EAP 5.1.0.

               

              13:48:30,687 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."Celcom.ear"."atg_bootstrap.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."Celcom.ear"."atg_bootstrap.war".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "atg_bootstrap.war" of deployment "Celcom.ear"

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_51]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_51]

                at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_51]

              Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/Users/calvin/apps/jboss-eap-6.1/standalone/deployments/Celcom.ear/atg_bootstrap.war/WEB-INF/ATG-INF/home/servers/atg_locksvr/j2ee/archive-cache/1377159609152-29/xmlfeed/WEB-INF/xtagsTaglib_20030721.tld" at [516,18]

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:143)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:122)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:101)

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

                ... 5 more

              • 4. Re: Failed to process jboss-app.xml
                Stephen Coy Master

                This major JBossAS release includes much stricter TLD parsing than what existed previously.

                 

                The chances are good that there is a genuine error in that TLD file in line 516.