[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-408) Request are not properly drained during undeploy
[
https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl...
]
Aaron Ogburn updated MODCLUSTER-408:
------------------------------------
Description:
mod_cluster doesn't properly drain requests during undeploy and/or shutdown.
org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0
requests.
It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is
selected by "internal_find_best_byrequests". So it doesn't count stickied
requests and allows shutdown to proceed even if stickied requests are in progress.
was:
mod_cluster doesn't properly drain requests during undeploy and/or shutdown. TRACE
logging shows JBoss receives a STOP-APP response indicating 0 requests.
It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is
selected by "internal_find_best_byrequests". So it doesn't count stickied
requests and allows shutdown to proceed even if stickied requests are in progress.
Request are not properly drained during undeploy
------------------------------------------------
Key: MODCLUSTER-408
URL: https://issues.jboss.org/browse/MODCLUSTER-408
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.2.8.Final
Reporter: Aaron Ogburn
Assignee: Jean-Frederic Clere
mod_cluster doesn't properly drain requests during undeploy and/or shutdown.
org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0
requests.
It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is
selected by "internal_find_best_byrequests". So it doesn't count stickied
requests and allows shutdown to proceed even if stickied requests are in progress.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)