Reply to comment

"proxy_balancer" | stickysession

Dear mailing list,

currently, we use the Apache2 version:
- Apache2 2.2.16 64bit
- standard "mod_proxy_balancer" module

with the following V-HOST configuration including a proxy balancer directive (with two Apache Tomcat instances behind):
<Proxy balancer://fs4server>
BalancerMember ajp:// loadfactor=100 retry=10 route=rb-wcmstc1
BalancerMember ajp:// loadfactor=100 retry=10 route=rb-wcmstc2

ProxySet stickysession=JSESSIONID
ProxySet lbmethod=byrequests
#ProxySet nofailover=On
ProxySet timeout=30

In production environment, we discover connection switches from "rb-wcmstc1" to "rb-wcmstc2" and vice versa (documented in the Tomcat-Logs) for the same Session-ID:

tomcat@<rb-wcmstc1>:/opt/tomcat/logs $ grep -i "5893975846599935313" *
log4j-catalina.log.13:TRACE 29.09.2010 14:16:58 ( Opening connection to, id=5893975846599935313
log4j-catalina.log.13:TRACE 29.09.2010 14:16:58 ( Server call from, id=5893975846599935313, clientLength=82, serverLength=79, serverResponseLength=1, 455 ms

DEBUG 29.09.2010 14:16:58 ( IO error with, port=1088, - java.
lang.IllegalStateException: Connection '5893975846599935313' not found
java.lang.IllegalStateException: Connection '5893975846599935313' not found
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(

Although, the "stickysession" attribute is set properly using the "JSESSIONID" cookie name and the Apache-Tomcat instances are up and running, the connection SWITCHES. Why?