maybe because tomcat2 needs to retrieve the session from memcached, are subsequent requests also slow? or just the first request after the failover?
-igor On Thu, Jun 3, 2010 at 11:06 AM, DmitryM <[email protected]> wrote: > > Hello, guys > > I managed to have Tomcat cluster working with memcached-session-manager > (http://groups.google.com/group/memcached-session-manager) from Martin. > > Everything works perfectly fine unless tomcats start getting shut down. > I have 2 tomcats running with the session replicated (see above). Then I > shut down one of them. > When on a page with ajax behavior after I click an ajax button the response > to the request gets delayed (about 2-3 seconds extra compared to the case > when all tomcats are live and running). > > I tried this with Wicket's SecondLevelCacheSessionStore(+ DiskPageStore, I > assume) and I also tried to use a Hazelcast-based PageStore (ex. from here: > http://wicketbyexample.com/apache-wicket-clustering-with-multiple-options/). > That bizarre delay happens in both cases. > > Can anyone please try to come up with some explanation what may be happening > in that case? > I guess, the scenario is as follows: > - tomcat cluster with proper session distribution in place, > - request hits tomcat1 and gets page with ajax button > - tomcat1 is shutdown > - ajax button is clicked > - request hits tomcat2 and gets processed successfully (but with delay) > > Thanks in advance, > Dmitry > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/SessionStore-life-cycle-in-cluster-tp2242105p2242105.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
