In workers.properties If you do use a balancer in workers.properties, there is an option to set "sticky" session when the balancer routes request to/from a worker.
# worker.balancer.sticky_session=true | false Not sure if the option can be use for regular workers as well, but might worth a try. Long www.edgesoft.ca ----- Original Message ----- From: "Vahid Hedayati" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Tuesday, March 21, 2006 9:13 AM Subject: Re: keeping same session via apache2 mod_jk2 and tomcat5 Hi Yep i know these was all for the purpose of testing Now that all virtual hosts are under 1 engine both sites shows the correct servlets but both still keep changing session ID the PersistentManager has been off for a long time too.. http://www.greenlightproductions.co.uk/servlets/SessionExample http://www.pro.org.uk/servlets/SessionExample also on greenlights virtual host <IfModule mod_jk.c> JkLogFile /var/log/apache2/mod_jk.log JkMount /servlets/* worker2 </IfModule> it is set to worker2 but on the the sessionExample shows worker1 (which i presume comes from the actual engine since there is now one set up with jvmRoute as worker1 but yet both sites with port 8180 seems to keep session id as it is http://www.pro.org.uk:8180/servlets/SessionExample http://www.greenlightproductions.co.uk:8180/servlets/SessionExample :( thanks vahid --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
