]
Stuart Douglas moved UNDERTOW-1141 to WFLY-9167:
------------------------------------------------
Project: WildFly (was: Undertow)
Key: WFLY-9167 (was: UNDERTOW-1141)
Affects Version/s: (was: 1.4.18.Final)
mod_cluster stop status is not updated in balancer/node resource
----------------------------------------------------------------
Key: WFLY-9167
URL:
https://issues.jboss.org/browse/WFLY-9167
Project: WildFly
Issue Type: Bug
Reporter: Bogdan Sikora
Assignee: Stuart Douglas
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 ).
{noformat}
[standalone@192.168.122.206:9990 /] /subsystem=modcluster:stop(waittime=-1)
{
"outcome" => "success",
"result" => {"session-draining-complete" => true}
}
{noformat}
However, status stays disabled, but functionallity is of a stopped one
{noformat}
"/karel" => {
"requests" => 0,
"status" => "disabled"
}
{noformat}
Apache httpd server as balancer correctly recognize stop status and stops contexts
{noformat}
/karel, Status: STOPPED Request: 0 Enable Disable
{noformat}
*Reproducing:*
# Set up undertow balancer with one worker
# Deploy an app to the worker
# Chech that app is correctly registered with balancer and that is enabled
# Stop the worker {noformat} /subsystem=modcluster:stop(){noformat}
# Watch if the context (deployed app) is moved to the stoped status
{noformat}/subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true,
recursive=true, recursive-depth=100){noformat}