> Don't most load balancers try to keep a session going to the same
> server? It might have a timeout setting that is less than your tomcat
> session timeout...
Cam said that they were using Bind, which is DNS and therefore is a simple
round-robin approach. Normally this should work in that a client will get
the IP address of say www.debuck.com and then will use that over and over
without doing additional DNS lookups. But, if the client were to do another
lookup, then Bind would likely have a one in <numberOfLoadBalancedIPAddrs>
of returning the original IP address.
You'll no doubt have to write a custom session handler for this and use a
method as described, where the session information is either stored in a
shared datastore or is in a shared directory in memory of some RMI service.
Some servlet environments provide persistent session management which likely
implement such a scheme on your behalf.
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
