sting
we setup a load-balancing config from apache, and our
simple test is to only enable 'tomcat 1' from apache, login - which should set
the session on 'tomcat 1'. Then reset the apache so
that 'tomcat 2' is the proxied host - and see if we're still logged in
e was creating a session for every
visitor - which sort of overwhelmed the cluster (all sessions are supposed to
be replicated to all cluster members - right?)... So
our adjustments just keep certain sessions from wasting cluster bandwidth if
they are of sufficiently short duration so as not to
wa
