Operation stop on mod_cluster worker disable all contexts (send disable status to balancer) for the duration of session draining. After the session is drained ( successfully or not ), worker stops all contexts ( send stop status to balancer ).

[standalone@192.168.122.206:9990 /] /subsystem=modcluster:stop(waittime=-1)
{
    "outcome" => "success",
    "result" => {"session-draining-complete" => true}
}

However, status stays disabled, but functionallity is of a stopped one

 "/karel" => {
   "requests" => 0,
   "status" => "disabled"
}

Apache httpd server as balancer correctly recognize stop status and stops contexts

/karel, Status: STOPPED Request: 0 Enable Disable

Reproducing:

1. Set up undertow balancer with one worker
2. Deploy an app to the worker
3. Chech that app is correctly registered with balancer and that is enabled
4. Stop the worker

    /subsystem=modcluster:stop()

5. Watch if the context (deployed app) is moved to the stoped status

   /subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100)