On 18.05.2010 12:35, JohnRiley wrote:
Hi, We are load balancing 3 non-clustered tomcat 6.0 servers with the mod_jk connector in apache 2.0. We have sticky sessions enabled and it works fine until one of the servers goes down. What happens then is that it start round-robin between the other two since none of them wants to accept the JSESSIONID with the route of the crashed tomcat server. How can I make one of the other servers to create a new session with its own jvmRoute for that tomcat? Because right now we have a huge problem when taking down a server for maintenance. The user will change server on each request until the server that is down for maintenance is back up again. Do we really have to setup the tomcats in a cluster to accomplish this?
Not sure I understand the real problem. If the app does "not accept" the sessionid, I would expect it to create a new session (and a new sessionid) using the correct local route.
Do you use emptySessionPath in the connector configuration inside server.xml?
Can't you add a simple servlet filter overwriting the JSESSIONID cookie if it's route doesn't match the local route?
Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
