从 Eclipse 部署 jbpm-console.war:找不到服务服务 jboss.ejb.default-资源适配器名称服务
Deployment jbpm-console.war from Eclipse: Service service jboss.ejb.default-resource-adapter-name-service not found
我可以使用 "ant start.demo," 成功启动 JBoss 服务器和 KIE workbench 但我想配置 Eclipse 以便我可以启动 JBoss 服务器和 Eclipse 中的 KIE workbench。我通过 Eclipse 中的 MarketPlace 下载了 JBoss,并创建了一个新的 JBoss 服务器。 Eclipse 中服务器的主目录是 wildfly-8.1.0.Final jbpm-installer 文件夹中的文件夹。
当我在 Eclipse 中启动 JBoss 服务器时,出现以下错误,说明 jbpm-console.war 文件无法启动(无法处理部署的 PARSE 阶段 "jbpm-console.war" caused by org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found. 有谁知道如何正确配置 Eclipse 以便 JBoss 服务器和 KIE workbench (jbpm-console) 可以在 Eclipse 中启动吗?
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
手动启动服务器时需要使用standalone-full配置文件。在这里查看我们通过安装程序启动服务器时使用的所有命令行参数,您可能想要复制这些:
https://github.com/droolsjbpm/jbpm/blob/6.2.0.Final/jbpm-installer/build.xml#L487
在 Eclipse 的 WildFly 配置中,我必须添加 -Dorg.kie.demo=false
和 -Dorg.kie.example=false
以便当 JBoss 服务器启动时,代码不会尝试提取示例 jbpm 文件来自 GitHub。此外,我还必须在 WildFly 服务器的 Eclipse 配置中从 "standalone.xml" 切换到 "standalone-full.xml"。
我可以使用 "ant start.demo," 成功启动 JBoss 服务器和 KIE workbench 但我想配置 Eclipse 以便我可以启动 JBoss 服务器和 Eclipse 中的 KIE workbench。我通过 Eclipse 中的 MarketPlace 下载了 JBoss,并创建了一个新的 JBoss 服务器。 Eclipse 中服务器的主目录是 wildfly-8.1.0.Final jbpm-installer 文件夹中的文件夹。
当我在 Eclipse 中启动 JBoss 服务器时,出现以下错误,说明 jbpm-console.war 文件无法启动(无法处理部署的 PARSE 阶段 "jbpm-console.war" caused by org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found. 有谁知道如何正确配置 Eclipse 以便 JBoss 服务器和 KIE workbench (jbpm-console) 可以在 Eclipse 中启动吗?
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
手动启动服务器时需要使用standalone-full配置文件。在这里查看我们通过安装程序启动服务器时使用的所有命令行参数,您可能想要复制这些: https://github.com/droolsjbpm/jbpm/blob/6.2.0.Final/jbpm-installer/build.xml#L487
在 Eclipse 的 WildFly 配置中,我必须添加 -Dorg.kie.demo=false
和 -Dorg.kie.example=false
以便当 JBoss 服务器启动时,代码不会尝试提取示例 jbpm 文件来自 GitHub。此外,我还必须在 WildFly 服务器的 Eclipse 配置中从 "standalone.xml" 切换到 "standalone-full.xml"。