I realize that sticky sessions always send requests from the same session to the same Tomcat instance. However, if my sample application isn't using a session (i.e. no cookies, URL rewriting, or hidden form fields), wouldn't every request be seen as a new session and distributed among Tomcats on a per-request basis (because in this case a session only lasts one request from the point of view of the servers).
Of course once I've enabled some sort of session handling, then I'd expect to see the behavior I see now. Correct me if I've misunderstood, but this is why I believe I'm not seeing expected behavior and am likely doing something wrong. Also, how might I view the load balancing of different sessions in action? I've cleared cookies and opened up a new browser window (even though I don't think it's necessary in this case because I'm not using sessions), but it still goes back to the same server. Any thoughts? Thanks. Tim Lucia wrote: > > Sticky sessions means exactly that. Stick the session to a particular > tomcat. If you shut down that tomcat, it should fail over to the other > tomcat(s) if you have properly set up your cluster. > > If you use synchronous replication you don't need sticky sessions as all > tomcats should have the session updates before the response is sent. > > Tim > >> -----Original Message----- >> From: lightbulb432 [mailto:[EMAIL PROTECTED] >> Sent: Saturday, April 21, 2007 5:49 PM >> To: users@tomcat.apache.org >> Subject: Sticky sessions not changing servers >> >> >> 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] > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Sticky-sessions-not-changing-servers-tf3624620.html#a10127879 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]
