application context is enabled to mod_cluster for servers that are started as suspended in the JBoss EAP 7.2 ------------------------------------------------------------------------------------------------------------ Key: WFLY-13074 URL: https://issues.redhat.com/browse/WFLY-13074 Project: WildFly Issue Type: Bug Components: mod_cluster, Web (Undertow) Affects Versions: 19.0.0.Beta1 Reporter: Chao Wang Assignee: Chao Wang Priority: Major Labels: downstream_dependency When a server that is running is suspended, the application contexts are stopped: {code:java} 2020-01-31 09:27:47,548 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 6) MODCLUSTER000008: Received stop context event for default-host:/appname 2020-01-31 09:27:47,548 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 6) MODCLUSTER000010: Sending DISABLE-APP for default-host:/appname 2020-01-31 09:27:47,550 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 6) MODCLUSTER000021: All pending requests drained from default-host:/appname in 0.0 seconds {code} From undertow loadbalancer: {code:java} 2020-01-31 09:24:55,828 DEBUG [io.undertow] (default task-1) UT005057: Sending MCMP response to destination: /127.0.0.1:44386, HTTP status: 200, Headers: {Content-Type=[text/plain; charset=ISO-8859-1]}, response: Type=STOP-APP-RSP,JvmRoute=slave:server1Alias=default-host,localhostContext=/appnameRequests=0 {code} But if a server is started as suspended, the contexts are enabled: {code:java} 2020-01-31 09:34:10,570 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 81) MODCLUSTER000005: Received add context event for default-host:/appname 2020-01-31 09:34:10,570 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 81) MODCLUSTER000007: Received start context event for default-host:/appname {code}