Oi João.
É. Eu parava quando não aparecia a aplicação. Não parei. Continuei e o servidor foi iniciado.
com alguns warnings como pode ser visto abaixo.
E não mostrou a aplicação agendamento-email na servers.
foi a única linha de discrepância com a sua tela.
Abaixo as últimas linhas do log com o warning.
16:30:35,727 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.4.2.Final (Apache CXF 3.3.9)
16:30:36,676 WARNING [io.netty.channel.DefaultChannelId] (MSC service thread 1-7) Failed to find the current process ID from ''; using a random value: 226750358
16:30:39,697 WARN [org.jboss.activemq.artemis.wildfly.integration.recovery] (MSC service thread 1-7) 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
16:30:39,702 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-7) AMQ151007: Resource adaptor started
16:30:39,703 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-7) IJ020002: Deployed: file://RaActivatoractivemq-ra
16:30:39,709 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
16:30:39,710 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
16:30:40,264 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
16:30:40,268 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Preview 23.0.0.Final (WildFly Core 15.0.0.Final) started in 16267ms - Started 334 of 575 services (351 services are lazy, passive or on-demand)
16:30:40,275 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
16:30:40,276 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990