-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.1.0.DR16
-
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 } }
Issue:
waittime is ignored. node/context is stopped right away.
17:17:26,725 DEBUG [io.undertow] (default task-21) UT005057: Sending MCMP response to destination: /192.168.122.196:59778, HTTP status: 200, Headers: {X-Powered-By=[Undertow/1], Server=[JBoss-EAP/7], Content-Type=[text/plain; charset=ISO-8859-1]}, response: Type=STOP-APP-RSP,JvmRoute=jboss-eap-7.1-2Alias=default-host,localhostContext=/clusterbenchRequests=0
- clones
-
UNDERTOW-1053 stop-context/stop waittime ignored
- Resolved
- is cloned by
-
JBEAP-10355 (7.0.x) stop-context/stop waittime ignored
- Closed
- is related to
-
JBEAP-10356 mod_cluster stop/stop-context(waittime=..) attribute description is wrong
- Closed