여러 WAR(웹 서비스)이 포함된 EAR이 있습니다. 이러한 WAR은 Wildfly의 HTTP 서버를 사용하여 배포 단계에서 서로 통신합니다. 현재 8.2.0, 10.0.0, 10.1.0을 문제없이 사용하고 있는데 최신 Wildfly로 업그레이드하고 싶습니다. 서버가 시작될 때 EAR이 배포 폴더에 있으면 Wildfly 11(Wldfly 20까지 테스트함)의 HTTP 서버가 배포 단계에서 응답하지 않는 것으로 나타났습니다. 그러나 서버가 먼저 시작된 다음 EAR을 배포 폴더에 넣으면 HTTP 서버가 응답하고 EAR이 올바르게 배포됩니다.
HTTP 서버가 배포 폴더에 있는 EAR로 서버가 시작될 때 배포 단계 중에 요청에 응답하도록 이 동작을 변경할 수 있습니까?
Wildfly 11 관련 로그(공지 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)