I've configured mod_jk and have sticky sessions, but every request is going to the exact same Tomcat instance and not the other instance. I've tried setting the loadbalancer method to both Request and Busyness, but they both do the same thing.
It works as expected when sticky sessions are disabled. Does this have to do with the fact that my Tomcat WAR isn't doing anything with cookies? Really the WAR in each Tomcat instance only has static pages and images, not really any dynamic stuff going on. Nonetheless, why am I not seeing even split in the jkstatus page of the sticky session requests when I create a new request? For example, if I open up a new browser window and delete browser cookies and make the same request, it still goes to the same instance. How else can I tell my setup that it's a new session that shouldn't remain sticky to the previous Tomcat instance? Thanks a lot. -- View this message in context: http://www.nabble.com/Sticky-sessions-not-changing-servers-tf3624620.html#a10121415 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
