On 19/05/2010 01:18, Steve Yates wrote: > G'day John, the strategy I would employ in your particular case would be > to utilise the JvmRouteBinderValve. Now the JvmRouteBinderValve was > designed to be used within a clustered environment I cannot see why it > cannot be configured stand-alone to simply detect for an incorrect route > and modify the client-side cookie appropriately.
Because the first thing that that Valve does is to look if clustering or a persistent manager is configured and does nothing neither is the case. Hence my previous response. See the source code for details. Mark > > RGS > SY > > On 5/18/2010 8:35 PM, 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? >> >> Best Regards >> >> John Riley >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
