-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR16, 7.1.0.DR17
-
None
-
User Experience
-
-
-
-
-
Cli operation description
[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
}
}
With default and non distributable context or draining strategy set to ALWAYS.
stop() or stop-context is called with waittime set to 0
Session drain
2017-05-10 09:18:21,953 INFO [org.jboss.modcluster] (management-handler-thread - 2) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 0 seconds.
Issue
This should immediately fail to drain session and send stop node/context to balancer.
However, it looks like it is waiting for session to timeout
Context/Node is disabled on balancer
"context" => {"/clusterbench" => {
"requests" => 0,
"status" => "disabled"
}}
- is blocked by
-
-
- Resolved
-
- is incorporated by
-
JBEAP-10839 Upgrade mod_cluster to 1.3.7.Final
-
- Closed
-
- is related to
-
-
- Closed
-
