For those interested.... This problem is resolved by ensuring that the 'Engine' definition in the Tomcat's server.xml configuration has a 'jvmRoute' attribute which matches the tomcatID in the channels being defined in apache's workers2.properties.
-----Original Message----- From: Claudio Pracilio [mailto:cpracilio@;sertan.net] Sent: Friday, November 08, 2002 2:19 PM To: 'Tomcat Users List' Subject: jk2 + sticky session Hello, I have the following environment: OS: RedHat 7.3 Apache 2.0.43 compiled with a worker mpm option jakarta-tomcat-connectors-4.1.12 - mod_jk2 jakarta-tomcat-4.1.12 I have successfully used the connector to connect Apache with one instance of Tomcat. With 2 instances of tomcat (on different ports), I have been able to get the load-balancing algorithm cycling between each tomcat server for each request. How do I make the session sticky, so that one instance of client Browser gets associated with the same Tomcat instance ? Regards, Claudio -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
