2
respostas

Servidor não sobe após configurar para enviar email de forma assincrona

bom dia. segui o curso e estou recebendo erro ao tentar subir o servidor após configurar para enviar email de forma assincrona.

Tentei usar as dicas que um aluno apresentou em outro topico, mas ainda não foi suficiente: https://cursos.alura.com.br/forum/topico-servidor-nao-sobre-depois-de-implementar-email-assincrono-68805

obs: voltei para as configurações padrão do wildfly 16, pois havia modificado pegando algumas coisas de jms do standalone.full.

até então no curso, estava funcionando tudo corretamente até antes de enviar o email. estou usando wildfly 16, java 8, mysql 8.0. segue o erro:

10:21:44,102 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."casadocodigojavaee.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."casadocodigojavaee.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "casadocodigojavaee.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
    at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Unknown Source)
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:652)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:248)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:156)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:83)
    at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:50)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
    ... 8 more

10:21:44,177 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "casadocodigojavaee.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"casadocodigojavaee.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"casadocodigojavaee.war\"
    Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
10:21:44,186 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 43) WFLYSRV0010: Deployed "casadocodigojavaee.war" (runtime-name : "casadocodigojavaee.war")
10:21:44,188 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.deployment.unit."casadocodigojavaee.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "casadocodigojavaee.war"

10:21:44,247 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
10:21:44,250 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
10:21:44,250 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
10:21:44,250 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 3843ms - Started 326 of 553 services (1 services failed or missing dependencies, 327 services are lazy, passive or on-demand)
2 respostas

Oi Rogério, tudo bem?

Acredito que você esteja usando o standalone normal e não o standalone-full.xml

Oi, Otavio. td e vc? duas perguntas:

  1. em que momento q eu configuro para usar o standalone-full?
  2. eu consigo mudar o standalone para full sem precisar reinstalar o wildfly 16 no eclipse? ou precisa apagar o server e adicionar de novo no eclipse ? Obrigado

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software