從Eclipse部署jbpm-console.war：找不到服務服務jboss.ejb.default-resource-adapter-name-service

Question

我可以使用“ant start.demo”成功啟動JBoss服務器和KIE工作台，但是我想配置Eclipse以便我可以在Eclipse中啟動JBoss服務器和KIE工作台。 我通過Eclipse中的MarketPlace下載了JBoss，並創建了一個新的JBoss服務器。 Eclipse中服務器的主目錄是jbpm-installer文件夾中的wildfly-8.1.0.Final文件夾。

當我在Eclipse中啟動JBoss服務器時，我收到以下錯誤，描述了jbpm-console.war文件無法啟動（無法處理由org.jboss.msc引起的部署“jbpm-console.war”的階段PARSE。 service.ServiceNotFoundException：找不到服務服務jboss.ejb.default-resource-adapter-name-service。有沒有人知道如何正確配置Eclipse，以便可以在Eclipse中啟動JBoss服務器和KIE工作台（jbpm-console）？

11:28:48,623 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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: JBAS018733: Failed to process phase PARSE of deployment "jbpm-console.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_75]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_75]
    at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_75]
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:668) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:278)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:244)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:89)
    at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processBeanMetaData(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:65)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.processDeploymentDescriptor(AbstractDeploymentUnitProcessor.java:143)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:84)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
    ... 5 more

11:28:48,627 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jbpm-console.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"jbpm-console.war\"
    Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
11:28:48,664 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "jbpm-console.war" (runtime-name : "jbpm-console.war")
11:28:48,665 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which 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: JBAS018733: Failed to process phase PARSE of deployment "jbpm-console.war"

11:28:53,876 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment jbpm-console.war (runtime-name: jbpm-console.war) in 4994ms
11:28:53,877 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
11:28:53,878 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
11:28:53,878 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 52549ms - Started 203 of 245 services (87 services are lazy, passive or on-demand)
11:28:54,771 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "jbpm-console.war" (runtime-name: "jbpm-console.war")
11:28:54,771 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."jbpm-console.war".PARSE

Answer 1

手動啟動服務器時，需要使用獨立完整配置文件。 看看這里看到我們通過安裝程序啟動服務器時使用的所有命令行參數，你可能想要復制它們： https ： //github.com/droolsjbpm/jbpm/blob/6.2.0.Final/jbpm-安裝/ build.xml文件＃L487

Answer 2

在Eclipse中的WildFly配置中，我必須添加-Dorg.kie.demo=false和-Dorg.kie.example=false以便在JBoss服務器啟動時，代碼不會嘗試從GitHub中提取示例jbpm文件。 此外，我還必須在WildFly服務器的Eclipse配置中從“standalone.xml”切換到“standalone-full.xml”。