1 Reply Latest reply on Mar 9, 2015 2:21 AM by Maciej Swiderski

    JBPM6.1-Final WAR not Deploying on Jboss EAP 6.3.0 and EAP 6.2.0

    Zahid Ahmed Prs Newbie

      I am unable to deploy the JBPM6 full-installer generated war file in to Jboss-EAP-6.3.0 and EAp-6.2.0.

      Problem Statement

      Whenever I deploy the generated WAR into Jboss-EAP-6.3.0 server, I get the following error. I have generated the war file from the jbpm-6.1.0.Final-installer-full.zip.

      I have taken the WAR from

        <i>jbpm-installer\lib\jbpm-console-6.1.0.Final </i> 

      and also tried with the

        <i> jbpm-installer\wildfly-8.1.0.Final\standalone\deployments\jbpm-console.war </i>

       

       

      18:00:30,162 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jbpm-console-6.1.0.Final.war".STRUCTURE: org.jbo

      ss.msc.service.StartException in service jboss.deployment.unit."jbpm-console-6.1.0.Final.war".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "jbpm-console-

      6.1.0.Final.war"

              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_72]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_72]

              at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_72]

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018774: Error loading jboss-all.xml from D:\DevelopmentWorks\A - JBPM CLEAN\jboss-eap-6.3\standalo

      ne\tmp\vfs\temp\temp55ebfbce84643028\content-8cd5d09c7231b0e8\META-INF\jboss-all.xml

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor.parse(JBossAllXMLParsingProcessor.java:153) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Fina

      l-redhat-19]

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor.parse(JBossAllXMLParsingProcessor.java:128) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Fina

      l-redhat-19]

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor.deploy(JBossAllXMLParsingProcessor.java:96) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Fina

      l-redhat-19]

              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

              ... 5 more

      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[18,3]

      Message: Unexpected element '{urn:jboss:weld:1.0}weld'

              at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)

              at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor$Parser.parseJBossElement(JBossAllXMLParsingProcessor.java:203) [jboss-as-server-7.4.0.Final-redha

      t-19.jar:7.4.0.Final-redhat-19]

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor$Parser.readElement(JBossAllXMLParsingProcessor.java:192) [jboss-as-server-7.4.0.Final-redhat-19.j

      ar:7.4.0.Final-redhat-19]

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor$Parser.readElement(JBossAllXMLParsingProcessor.java:176) [jboss-as-server-7.4.0.Final-redhat-19.j

      ar:7.4.0.Final-redhat-19]

              at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)

              at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)

              at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor.parse(JBossAllXMLParsingProcessor.java:148) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Fina

      l-redhat-19]

              ... 8 more

       

       

      18:00:30,189 ERROR [org.jboss.as.server] (HttpManagementService-threads - 2) JBAS015870: Deploy of deployment "jbpm-console-6.1.0.Final.war" was rolled back with the following fai

      lure message:

      {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console-6.1.0.Final.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"j

      bpm-console-6.1.0.Final.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"jbpm-console-6.1.0.Final.war\"

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018774: Error loading jboss-all.xml from D:\\DevelopmentWorks\\A - JBPM CLEAN\\jboss-eap-6.3\\

      standalone\\tmp\\vfs\\temp\\temp55ebfbce84643028\\content-8cd5d09c7231b0e8\\META-INF\\jboss-all.xml

          Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[18,3]

      Message: Unexpected element '{urn:jboss:weld:1.0}weld'"}}

      18:00:30,192 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jbpm-console-6.1.0.Final.war (runtime-name: jbpm-console-6.1.0.Final.wa

      r) in 3ms

      18:00:30,193 INFO  [org.jboss.as.controller] (HttpManagementService-threads - 2) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.deployment.unit."jbpm-console-6.1.0.Final.war".STRUCTURE

        • 1. Re: JBPM6.1-Final WAR not Deploying on Jboss EAP 6.3.0 and EAP 6.2.0
          Maciej Swiderski Master

          you're trying to deploy wildfly version of jBPM on EAP and that won't work mainly due to Wildfly is JEE7 and EAP 6 is JEE 6 and there are different way to initialize components of the application. Use container specific war files that you can either download manually from JBoss Maven repository or reconfigure installer via build.properties to install on top of EAP.

           

          Please note that 6.1.0.Final is targeting EAP 6.1. Use jBPM 6.2.0.Final to work on EAP 6.3.

           

          HTH

          1 of 1 people found this helpful