Jboss服务器错误:无法启动服务jboss.deployment.unit。“ jbpm-console.war”


狗头军师
2025-03-17 11:22:34 (25天前)

启动jboss服务器时,出现错误无法启动服务jboss.deployment.unit。“ jbpm-console.war”。但是当我使用start.demo运行jbpm6演示时,它的工作正常。

  1. 23:43:41,042 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: 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: Failed to process phase PARSE of deployment "jbpm-console.war"
  2. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
  3. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
  4. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
  5. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
  6. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
  7. at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
  8. Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
  9. at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
  10. at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:273)
  11. at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:244)
  12. at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:88)
  13. at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processBeanMetaData(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:65)
  14. at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.processDeploymentDescriptor(AbstractDeploymentUnitProcessor.java:143)
  15. at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:84)
  16. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
  17. ... 5 more
  18. 23:43:41,104 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015951: Admin console listening on http://127.0.0.1:9990
  19. 23:43:41,104 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jbpm-console.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".PARSE: Failed to process phase PARSE of deployment \"jbpm-console.war\""}}
  20. 23:43:41,104 ERROR [org.jboss.as] (MSC service thread 1-6) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 49681ms - Started 344 of 423 services (1 services failed or missing dependencies, 76 services are passive or on-demand)
  21. 23:43:41,104 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "dashboard-builder.war" was rolled back with no failure message
4 条回复
  1. 1# 狗头军师 | 2020-08-23 14-39

    尝试用./standalone.sh -c standalone-full.xml或任何其他允许您从完整配置文件开始的替代方法凝视jboss

  2. 2# 狗头军师 | 2020-08-23 14-39

    尝试用./standalone.sh -c standalone-full.xml或任何其他允许您从完整配置文件开始的替代方法凝视jboss

  3. 3# v-star*위위 | 2020-08-23 14-41

    Activiti是一个有趣的项目,其原因如下:

    他们打算使发动机商品化。因此,他们使用Apache软件许可。到目前为止,已有多家公司支持该项目。“业务模型”在某种程度上类似于OpenStack所使用的模型。

    拥有一个可供所有人使用的BPMN 2.0引擎是很有意义的。这确实包括jBoss(但我怀疑它们会很快切换)。

登录 后才能参与评论