tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard W. Smith, Jr." <>
Subject Re: Help in diagnosing server unresponsiveness
Date Wed, 06 Feb 2013 01:29:47 GMT

On Sun, Feb 3, 2013 at 12:39 PM, Christopher Schultz
<> wrote:
> Hash: SHA256
> Howard,
> If your requirements allow for users to have to re-authenticate when
> you have a failover-event, then I highly recommend that you use
> sticky-sessions /without/ session replication: performance will be
> much better that way (and it's easier to configure).

this is very interesting but somewhat of a concern as well. does
failover occur when one tomcat-and-web-app instance is taking a long
time serving one request? there are a few places/pages in my web app
that does some heavy lifting (reports that execute SQL SELECT, and
yes, I am using indexes along with statement caching, etc...), and
i've seen my app failover with a 404 error (i currently only have one

> Well, if you can tolerate re-auth on failover, then there's nothing to
> do at all: simply enable sticky-sessions and let it happen. Failovers
> should be rare, anyway, right?

sticky sessions sound nice and I would love to give it a try, but
honestly, i don't think the endusers want to have to re-auth on
failover. just today, I read on the atmosphere list that sticky
sessions are required for using atmosphere with/in clusters. i'm
definitely using atmosphere, but not using sticky sessions (or
clusters) yet.  :(

> - -chris
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools -
> Comment: Using GnuPG with Thunderbird -
> yYEAoIqunDmRHiQvzLrtR+5UcmwTKIt0
> =L0xm
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message