Hi Arunkumar, The failover is working. What I need is the tomcat instance to which failover occurs assumes ownership of the sticky session, by that the session id has to be changed to use that tomcat instance's jvmRoute and cookie has to be reset, otherwise it is no longer sticky session since requests for tha session will be sent to ANY of the other tomcat instances configured by load balancing. I believe this transfer of sticky session ownership done by renaming of the session and resetting the cookie is performed by JvmRouteBinderValve which is configured as part of a Cluster configuration. My problem is that I'm not using cluster session replication because my environment doesn't support multicast. I'm using PersistentManager for session persistence using jdbc as mentioned. I don't think it is possible to successfully configure a Cluster in this case (no multicast and using PersistentManager instead of session replication) but a Cluster configuration is required to configure JvmRouteBinderValve. I'm wondering what my options are in this case. Do I have to write my own valve to do what JvmRouteBinderValve does but that works without a cluster configuration? Is my understanding correct?
Regards, Len -----Original Message----- From: Arunkumar Janarthanan [mailto:arunkumar.webad...@gmail.com] Sent: March-27-10 5:36 PM To: Tomcat Users List Subject: Re: sticky session failover Len, Do you have a the "nofailover" parameter disabled ? this can help users continue served by the working tomcat instances in-case of the tomcat instance which cookie parameter set fails / not available. <Proxy balancer://abc> BalancerMember ajp://prod1:8081 route=app1 BalancerMember ajp://prod2:8081 route=app2 BalancerMember ajp://prod3:8081 route=app3 ProxySet stickysession=JSESSIONID ProxySet nofailover=Off </Proxy> On Fri, Mar 26, 2010 at 5:21 PM, Len Takeuchi <ltakeu...@jostleme.com>wrote: > Hello, > > I have apache load balancing a number of tomcat instances using mod_jk > using sticky session. This is all working with the session id having > the jvmRoute appended. I am storing the session using persistent > manager using jdbc. I want to have failover for session as supported by > JvmRouteBinderValve. Is this possible to set up in an environment where > multicast is not supported? Do I need to set up a Cluster though I > don't need session replication since I'm using persistent manager for > session storage so all tomcat instances have access to session data? > What I want is just the JvmRouteBinderValve behavior of changing the > session id to the new jvmRoute and setting cookie when a tomcat instance > receives a session request from a different jvmRoute. > > Regards, > Len > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
