]
Jan Kašík commented on WFLY-11198:
----------------------------------
In my scenario, there are 3 workers (cluster nodes). Before sending those 10 requests I am
also sending session request and verifying that session on stopped worker is still
active.
Session draining on stopped worker won't complete if further
requests are made on balancer
------------------------------------------------------------------------------------------
Key: WFLY-11198
URL:
https://issues.jboss.org/browse/WFLY-11198
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 15.0.0.Alpha1
Reporter: Jan Kašík
Assignee: Radoslav Husar
Priority: Major
When disabling worker with {{/subsystem=modcluster/proxy=default:stop(waittime=0)}}, the
contexts are switched to {{disabled}} state. If there no further requests (on the same
context which session currently times out) are made on a balancer, session correctly times
out, contexts switch to {{stopped}} state and everything is OK.
However, when I run same stop operation, wait until contexts are switched into
{{disabled}} state and in time in which sessions time out I make more requests on
balancer, contexts will never switch to {{stopped}} state and session draining never
completes. This happens intermittently (~60% of cases with 10 requests made after
{{disabled}} state is in place).