Bug 1136976

Description of problem:

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.


Version-Release number of selected component (if applicable):

mod_cluster 1.2.9.Final


How reproducible:

Very


Steps to Reproduce:

1. To exacerbate the issue, run httpd in prefork with a config forcing new processes every request:

StartServers         1
MaxClients         150
MinSpareServers      1
MaxSpareServers     1 
MaxRequestsPerChild  1

2. Set up mod_cluster with "CreateBalancers 1":

CreateBalancers 1
...
ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
ProxyPassReverse / balancer://mycluster/

3. Load up httpd with requests (they should all provide a stickied session) and check for breaks in stickiness. You can confirm the bug occurs also with one node by checking for occurrences of "proxy: byrequests balancer DONE" debug messages for what should be stickied requests.


Actual results:

Sticky sessions can break in new processes


Expected results:

Sticky sessions is maintained

Additional info: