As with most load balancers, I assumed by "stickysession" we were talking about balancing based only on the value of a cookie, but as far as I've been able to tell, that is not the case. On 2.2.3, with a configuration of: ProxyRequests Off ProxyPreserveHost On ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=On timeout=120 <Proxy balancer://cluster/> BalancerMember https://srv1.ivytech.edu:443 min=10 BalancerMember https://srv2.ivytech.edu:443 min=10 </Proxy> I'm finding that there really is no session affinity to the members at all. There are a few various posts in various archives with the same findings, but with no definite conclusion as to whether or not the balancer's doing this by design... If we instead configure the BalancerMember's with routes and configure the Tomcat with jvmRoutes accordingly, everything works as expected, but without route specified, it's as if there is no session affinity at all. So is mod_proxy_balancer intended to be a Tomcat-only feature, or are we dealing with a bug here? (Or, *shudder,* have I incorrectly configured something? :)) I'd be happy to provide debug logs if it seems appropriate. Thanks, John -- John Madden Sr. UNIX Systems Engineer Ivy Tech Community College of Indiana jmadden@xxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|