-
Bug
-
Resolution: Done
-
Major
-
7.1.0.ER1
-
None
[4:20 PM] Radoslav Husar: Also, the mgmt operation result doesn't provide the resulting status of stopping, i.e. if draining was complete
[4:20 PM] Radoslav Husar:
[4:20 PM] Radoslav Husar:
[standalone@localhost:9990 /] /subsystem=modcluster:stop(waittime=10
[4:21 PM] Radoslav Husar:
16:19:20,809 INFO [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds.
16:19:30,814 WARN [org.jboss.modcluster] (management-handler-thread - 3) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds
- clones
-
WFLY-9026 mod_cluster stop/stop-context operation results do not inform whether session draining was successful
- Closed
- relates to
-
JBEAP-10821 mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful
- Closed