web-dev-qa-db-fra.com

Erreur du serveur Jboss: échec du démarrage du service jboss.deployment.unit. "Jbpm-console.war"

Lors du démarrage du serveur jboss, il donne une erreur Échec de démarrage du service jboss.deployment.unit. "Jbpm-console.war". Mais lorsque j'utilise la démo jbpm6 en utilisant start.demo, cela fonctionne bien.

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
javajbossjboss7.xjbpm
18
user2848031

essayez de regarder jboss avec ./standalone.sh -c standalone-full.xml ou toute autre alternative qui vous permet de commencer avec le profil complet

17
salaboy

J'ai eu exactement le même problème, j'ai constaté que je manquais

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

en dessous de

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

dans standalone/configuration/standalone.xml

7
Sagar

Meilleure solution: Aller au dossier jboss-as-7.1.1.Final\standalone\deployments et supprimer tous les fichiers existants ....

Exécutez à nouveau votre problème sera résolu

6
Jagraj Singh
  1. supprimez votre dossier de projet sous C:\....\wildfly-9.0.1.Final\standalone\deployments\YOUR-PROJEKT-FOLDER
  2. redémarrez votre serveur wildfly
2
Yavuz

vous devez exécuter standlone.bat ou .sh avec le commutateur -c standalone-full.xml peut fonctionner.

1
Alireza Alallah

J'ai eu un problème similaire, mon erreur était:

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]

J'utilise jboss et glassfish donc j'ai changé le web.xml aux éléments suivants:

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

Au lieu de:

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

J'espère que ce travail pour vous.

0
chandrakant