【问题标题】:Jboss server error : Failed to start service jboss.deployment.unit."jbpm-console.war"Jboss 服务器错误:无法启动服务 jboss.deployment.unit。“jbpm-console.war”
【发布时间】:2014-03-13 08:00:55
【问题描述】:

当启动 jboss 服务器时,它给出一个错误 Failed to start service jboss.deployment.unit."jbpm-console.war"。但是当我使用 start.demo 运行 jbpm6 演示时,它工作正常。

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"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
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:447) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:273)
        at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:244)
        at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:88)
        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:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        ... 5 more

23:43:41,104 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015951: Admin console listening on http://127.0.0.1:9990
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\""}}
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)
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

【问题讨论】:

    标签: java jboss jboss7.x jbpm


    【解决方案1】:

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

    【讨论】:

    • 我同意这个答案,但只是一个旁注——不要忘记standalone-full.xml 不会配置开箱即用的 jbpm 数据源。
    • @salaboy,谢谢.. 我对这个错误感到沮丧好几个小时,谷歌搜索并发现在standalone-full.xml 中添加 .. 而没有运行该文件服务器启动..但最后我运行成功...再次感谢...
    【解决方案2】:

    最佳解决方案:转到 jboss-as-7.1.1.Final\standalone\deployments 文件夹并删除所有现有文件....

    再次运行你的问题就解决了

    【讨论】:

      【解决方案3】:

      我遇到了完全相同的问题,发现我失踪了

      <mdb>  
        <resource-adapter-ref resource-adapter-name="hornetq-ra"/>  
        <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>  
      </mdb>  
      

      <subsystem xmlns="urn:jboss:domain:ejb3:1.2">  
      

      在独立/配置/standalone.xml 中

      【讨论】:

      • 你能解释一下吗?这些标签有什么作用……这些名称是什么意思?
      【解决方案4】:
      1. 删除C:\....\wildfly-9.0.1.Final\standalone\deployments\YOUR-PROJEKT-FOLDER下的项目文件夹
      2. 重启你的wildfly服务器

      【讨论】:

        【解决方案5】:

        您应该使用 -c Standalone-full.xml 开关运行 standlone.bat 或 .sh 可能是工作。

        【讨论】:

          【解决方案6】:

          我遇到了类似的问题,我的错误是:

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException:org.glassfish.jersey.servlet.ServletContainer from [Module "deployment.RESTful_Services_CRUD.war:main" from Service Module Loader]
          

          我使用jbossglassfish,所以我将web.xml 更改为以下内容:

          <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
          

          代替:

          <servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>
          

          希望这对你有用。

          【讨论】:

            猜你喜欢
            • 2014-11-10
            • 2014-05-19
            • 1970-01-01
            • 2016-06-14
            • 2016-11-09
            • 2016-10-29
            • 2013-02-23
            • 2021-04-05
            • 1970-01-01
            相关资源
            最近更新 更多