4
respostas

WILDFLY não inicia.

Após seguir as orientações da aula para configuração de e-mail asincrono, o Wildfly não sobe mais.

segue meu git com o realizado : https://github.com/rbaselio/casadocodigo

18:16:09,513 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "casadocodigo.war" (runtime-name: "casadocodigo.war")
18:16:09,623 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."casadocodigo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."casadocodigo.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "casadocodigo.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
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:669)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:274)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:154)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:81)
    at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:57)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
    ... 5 more

18:16:09,623 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"casadocodigo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"casadocodigo.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"casadocodigo.war\"
    Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
18:16:09,637 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "casadocodigo.war" with deployment "casadocodigo.war"
18:16:09,638 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.undertow.deployment.default-server.default-host./casadocodigo
      service jboss.deployment.unit."casadocodigo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."casadocodigo.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "casadocodigo.war"
4 respostas

Oi Roberto, não consegui descobri o erro ainda... Se você retira a configuração do email tudo funciona? Meu chute é que durante a configuração alguma coisa foi editada sem querer e um módulo foi perdido.

se eu retirar a parte do e-mail, tudo funciona novamente.

Oi Roberto, a exception em si não me disse muita coisa...

O que eu faria: já existe uma versão standalone.xml no seu wildfly que tem uma configuração de email... eu usaria ela e faria apenas as alterações necessárias.

Eu resolvi o problema. Ao inves de iniciar o Wildfly com o standalone.xml, iniciei com o standalone-full.xml. Mas qual a diferença? A Alura tem algum curso voltado para o Jbooss/Wildfly???