Temos um EAR com vários WARs (serviços web). Esses WARs conversam entre si durante a fase de implantação usando o servidor HTTP do Wildfly. Estamos usando 8.2.0, 10.0.0 e 10.1.0 sem problemas no momento, mas gostaríamos de atualizar para o Wildfly mais recente. Percebi que o servidor HTTP do Wildfly 11 em diante (testei até o Wldfly 20) não está respondendo durante a fase de implantação se o EAR estiver na pasta de implantação quando o servidor for iniciado. No entanto, se o servidor for iniciado primeiro e depois eu colocar o EAR na pasta de implementação, o servidor HTTP responderá e o EAR será implementado corretamente.
É possível alterar esse comportamento, para que o servidor HTTP responda às solicitações durante a fase de implantação também quando o servidor for iniciado com o EAR colocado na pasta de implantações?
Registros relevantes do Wildfly 11 (aviso Resuming server):
wildfly2_1 | 08:37:14,606 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /wildfly/wildfly-11.0.0.Final/standalone/deployments
wildfly2_1 | 08:37:14,610 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ojdbc7.jar" (runtime-name: "ojdbc7.jar")
wildfly2_1 | 08:37:14,610 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "mysql-connector-java-5.1.6.jar" (runtime-name: "mysql-connector-java-5.1.6.jar")
wildfly2_1 | 08:37:14,610 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "sqljdbc4.jar" (runtime-name: "sqljdbc4.jar")
wildfly2_1 | 08:37:14,946 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 10.100.1.131:8443
wildfly2_1 | 08:37:15,052 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
wildfly2_1 | 08:37:15,435 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
wildfly2_1 | 08:37:15,460 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
wildfly2_1 | 08:37:15,477 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
wildfly2_1 | 08:37:15,533 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = sqljdbc4.jar
wildfly2_1 | 08:37:15,536 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.6.jar
wildfly2_1 | 08:37:15,543 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = ojdbc7.jar
wildfly2_1 | 08:37:15,546 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/ShakeSpeare
wildfly2_1 | 08:37:15,732 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final
wildfly2_1 | 08:37:16,027 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started client-mappings cache from ejb container
wildfly2_1 | 08:37:16,122 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "ojdbc7.jar" (runtime-name : "ojdbc7.jar")
wildfly2_1 | 08:37:16,122 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "mysql-connector-java-5.1.6.jar" (runtime-name : "mysql-connector-java-5.1.6.jar")
wildfly2_1 | 08:37:16,123 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "sqljdbc4.jar" (runtime-name : "sqljdbc4.jar")
wildfly2_1 | 08:37:16,188 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
wildfly2_1 | 08:37:16,193 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
wildfly2_1 | 08:37:16,194 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
wildfly2_1 | 08:37:16,194 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) started in 5708ms - Started 458 of 688 services (357 services are lazy, passive or on-demand)