[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-427) mod_cluster can break stickiness for the first request on new child processes

[Aaron Ogburn (JIRA)]

Aaron Ogburn created MODCLUSTER-427:
---------------------------------------

             Summary: mod_cluster can break stickiness for the first request on new child processes
                 Key: MODCLUSTER-427
                 URL: https://issues.jboss.org/browse/MODCLUSTER-427
             Project: mod_cluster
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Native (httpd modules)
    Affects Versions: 1.3.1.Alpha1, 1.2.9.Final
         Environment: -JBoss EAP 6.3.0
            Reporter: Aaron Ogburn
            Assignee: Jean-Frederic Clere


mod_cluster can break stickiness for the first request on new child processes.  It looks like this occurs specifically when "CreateBalancers 1" is used.  Prefork typically makes this much worse as well.

My debugging showed that the proxy_balancer would exist, but it would essentially be empty in the new child process.  find_session_route/find_route_worker would be called as expected, but the for loop in find_route_worker wasn't even doing anything because balancer->workers->nelts was 0.  The balancer would then finally be populated in the new child when the first request hits internal_find_best_byrequests and calls update_workers_node.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)