On 18/05/2010 11: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?
No, but I don't see how to do this with mod_jk. If you were using mod_proxy_http or mod_proxy_ajp then setting nofailover=On on your ProxyPass directive should do the trick. An option that should work with mod_jk (although it is a hack) would be to configure a PersistentManager that just persisted local sessions to disk with a JvmRouteBinderValve. Or you could write a valve/filter that invalidated the session and created a new one if it detected that the route was wrong. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
