Description of problem: When I start the brms ER5, I see the following error when start up. 16:31:38,947 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-15) MSC000001: Failed to start service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "kie-server.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-18.jar:7.5.0.Final-redhat-18] 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_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] 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:625) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:275) at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:155) at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:82) at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58) at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-18.jar:7.5.0.Final-redhat-18] ... 5 more 16:31:42,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry avalon-framework-4.2.0.jar in /home/rzhang/lab/1brms6/6.1.0/brms-6.1.0.ER5/jboss-eap-6.4/standalone/deployments/business-central.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. kie-server-...war can start in BPMSuite without problem. And kie-server in ER4 seems also have no problem with EAP 6.3 and 6.4. It seems there is some service or configuration is required for kie-server run on EAP. This needs further investigation. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
As of 6.1.0.ER5 the exec. server supports also JMS (with the help of MDB). The server needs to be started with standalone-full profile (or the default profiles needs to be tweaked, similarly as for BPM Suite).
This issue is resolved going forward. The standalone*.xml have the mdb and jms configuration defined in both the zip assembly and the installer.
Taking this issue while Ryan is on PTO.
This should have been fixed since ER5.
Verified by starting BRMS installed from ZIP assembly and also installed by installer. Also checked standalone.xml files in both installations.