2 Replies Latest reply on Jul 17, 2016 7:59 AM by Abhijit Humbe

    JBPM Wildfly Version

    Tony Gunter Newbie

      I am evaluating JBPM for a new project.  As a proof of concept, I spun up a quick Spring boot application to exercise the JBPM API through restful services with the idea that I could take these Autowired classes and simply drop them into the actual application at a future date.  The problem is that JBoss Wildfly 8.x has a known bug that throws null pointer exceptions for the HttpResponse headers with Spring Boot applications.  JBoss' Jira instance says this is fixed in 9.x and above.  So I downloaded Wildfly 10 and sure enough the Spring Boot application works fine (JBPM calls stubbed at the moment).

       

      Questions:

      1) Out of curiosity, why is the latest and greatest JBPM release out of sync with the latest and greatest Wildfly release?

      2) Can I deploy a JBPM application on Wildfly 9 or 10?  I prefer 10 since that appears to be what the application developers are going to use.

      3) If so, what are the steps to deploy to Wildfly 9 or 10?  I tried it just to verify it wouldn't work, and here is the exception I get when I do so:

       

      016-07-07 15:49:21,387 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jbpm-console.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "jbpm-console.war"

      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

      at java.lang.Thread.run(Thread.java:745)

      Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found

      at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:669)

      at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:274)

      at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:243)

      at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:88)

      at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processBeanMetaData(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:64)

      at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.processDeploymentDescriptor(AbstractDeploymentUnitProcessor.java:138)

      at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:79)

      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

      ... 5 more

        • 1. Re: JBPM Wildfly Version
          Tony Gunter Newbie

          Follow up:  that stack trace was me just dropping the jbpm-console.war file into a Wildfly 10 deployment directory.  I tried instead to change the jboss.server version in build.properties to 10.0.0 and repeating the install.  After doing so, I get this stack trace when it attempts to deploy the war file:

           

          2016-07-07 17:18:51,911 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jbpm-console.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "jbpm-console.war"

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

          at java.lang.Thread.run(Thread.java:745)

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file C:\tmp\jbpm-installer\wildfly-10.0.0.Final\standalone\tmp\vfs\temp\temp40a713e3fcd9db15\content-129c6e3cd3735ad6\WEB-INF\bpms-jms.xml

          at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

          ... 5 more

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file C:\tmp\jbpm-installer\wildfly-10.0.0.Final\standalone\tmp\vfs\temp\temp40a713e3fcd9db15\content-129c6e3cd3735ad6\WEB-INF\bpms-jms.xml

          at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)

          ... 6 more

          Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]

          Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'

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

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

          at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)

          ... 6 more

          • 2. Re: JBPM Wildfly Version
            Abhijit Humbe Master

            I think jBPM 6.4 is not yet compatible with Wildfly 10/ JBoss EAP 7. I will suggest you to try with Wildfly8/ JBoss AS 7 release.