[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated MODCLUSTER-408:
--------------------------------------
    Component/s: Native (httpd modules)
                     (was: Core & Container Integration (Java))


> Requests are not properly drained during undeploy
> -------------------------------------------------
>
>                 Key: MODCLUSTER-408
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-408
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Native (httpd modules)
>    Affects Versions: 1.2.8.Final
>            Reporter: Aaron Ogburn
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.2.10.Final, 1.3.1.Alpha1
>
>
> mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP.  org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained.
> 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.3.11#6341)