Erro ao acessar http://localhost:8080/agendamento-email-0.0.1-SNAPSHOT/emails

Thales, bom dia. A aplicação está deployada no servidor? Percebi também que está faltando a porta do server.

Tenta assim: http://127.0.0.1:8080/agendamento-email-0.0.1-SNAPSHOT/emails.

João. O mesmo problema. Embora já esteja tudo aparentemente perfeito... arquivos, packages .... Mas não está acontecendo o deploy. Log completo abaixo. Obrigado.

Não cabe. Muita coisa. A linha que fica diferente é do warning abaixo:

06:26:54,420 WARNING [io.netty.channel.DefaultChannelId] (MSC service thread 1-7) Failed to find the current process ID from ''; using a random value: -413457225

Então fiz os testes, erro persiste.

08:37:09,324 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. 08:37:09,325 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) Queuing requests. 08:37:09,325 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting 08:37:09,416 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\Thales Ernane\Documents\wildfly-preview-23.0.0.Final\standalone\deployments 08:37:09,740 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "agendamento-email-0.0.1-SNAPSHOT.war" (runtime-name: "agendamento-email-0.0.1-SNAPSHOT.war") 08:37:10,343 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete 08:37:10,627 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 08:37:11,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 08:37:11,335 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0007: Registered connection factory java:/JmsXA 08:37:12,542 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 08:37:19,053 WARNING [io.netty.channel.DefaultChannelId] (MSC service thread 1-2) Failed to find the current process ID from ''; using a random value: -1248643485 08:37:19,796 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.4.2.Final (Apache CXF 3.3.9) 08:37:22,709 WARN [org.jboss.activemq.artemis.wildfly.integration.recovery] (MSC service thread 1-2) AMQ122018: Could not start recovery discovery on XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&localAddress=127-0-0-1&useNio=true&host=localhost&useNioGlobalWorkerPool=true], discoveryConfiguration=null, username=guest, password=****, JNDI_NAME=java:/JmsXA], we will retry every recovery scan until the server is available 08:37:22,729 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-2) AMQ151007: Resource adaptor started 08:37:22,729 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatoractivemq-ra 08:37:22,731 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA] 08:37:22,731 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory 08:37:33,027 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 105) ISPN000128: Infinispan version: Infinispan 'Corona Extra' 11.0.9.Final 08:37:34,067 INFO [org.infinispan.CONFIG] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 08:37:34,069 INFO [org.infinispan.CONFIG] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 08:37:34,667 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 105) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller' 08:37:35,872 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 105) WFLYCLINF0002: Started http-remoting-connector cache from ejb container 08:37:36,284 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 106) WFLYUT0021: Registered web context: '/agendamento-email-0.0.1-SNAPSHOT' for server 'default-server' 08:37:36,689 INFO [org.jboss.as.server] (ServerService Thread Pool -- 69) WFLYSRV0010: Deployed "agendamento-email-0.0.1-SNAPSHOT.war" (runtime-name : "agendamento-email-0.0.1-SNAPSHOT.war") 08:37:37,446 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 08:37:37,449 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Preview 23.0.0.Final (WildFly Core 15.0.0.Final) started in 147417ms - Started 438 of 641 services (355 services are lazy, passive or on-demand) 08:37:37,540 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 08:37:37,541 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

Você consegue acessar a sua admin console? Esse endereço aqui: http://127.0.0.1:9990.

Se colocar http://localhost:8080/agendamento-email-0.0.1-SNAPSHOT/emails acontece o mesmo problema?

Quando faço o teste com http://localhost:8080/agendamento-email-0.0.1-SNAPSHOT/emails.

Apresenta erro:

Not Found

Quando faço o teste com http://127.0.0.1:9990.

Welcome to WildFly Your WildFly Application Server is running. However you have not yet added any users to be able to access the admin console.

To add a new user execute the add-user.bat script within the bin folder of your WildFly installation and enter the requested information.

By default the realm name used by WildFly is "ManagementRealm" this is already selected by default.

After you have added the user follow this link to Try Again.

Você pode subir seu código no github para eu da uma olhada?

João consegui resolver era a versão mesmo do Wildfly que estava usando 23 e não a 20, baixei a versão correspondente e funcionou, valeu vou continuar com as aulas, obrigado pela ajuda, estou gostando do curso, espero agregar muito meu conhecimento, grato !

Bom dia.

Também funcionou pra mim. Também estava usando a 23. Baixei um WildFly 20 e funcionou. Não gostei é de não funcionar em versões posteriores... Mas... dá para acompanhar o curso.

Obrigado.