[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-596) mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful

mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful ----------------------------------------------------------------------------------------------------- Key: MODCLUSTER-596 URL: https://issues.jboss.org/browse/MODCLUSTER-596 Project: mod_cluster Issue Type: Bug Components: Core & Container Integration (Java) Affects Versions: 1.3.6.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 2.0.0.Alpha1, 1.3.7.Final CLI operation description {noformat} [standalone@localhost:9990 /] /subsystem=modcluster/:read-operation-description(name=stop { "outcome" => "success", "result" => { "operation-name" => "stop", "description" => "Tell reverse proxies that all contexts on the node can't process requests.", "request-properties" => {"waittime" => { "type" => INT, "description" => "Timeout to wait for all contexts to stop.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => 10, "unit" => "SECONDS" }}, "reply-properties" => {}, "read-only" => false, "runtime-only" => true } } {noformat} With default and non-distributable context or draining strategy set to ALWAYS. * stop() or stop-context is called * Disable creating any new session by sending DISABLE-APP command to balancer {noformat} "context" => {"/clusterbench" => { "requests" => 0, "status" => "disabled" }} {noformat} * Session drain {noformat} 2017-05-10 09:19:09,956 INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. {noformat} * Session timeout is 5 minutes so it fails {noformat} 2017-05-10 09:26:05,081 WARN [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds {noformat} *_+{color:red}Issue{color}+_* * Stop-app should be sent to balancer to stop context/node, but node/context stays disabled. This happens even if session drain is successful. {noformat} "context" => {"/clusterbench" => { "requests" => 0, "status" => "disabled" }} {noformat}