We use BigIP from F5 Networks. It does handle session mapping across server pools ver well. We have a rule set that ensures a request from a given user is mapped to the same server. The F5 folks helped us out in getting things setup and running. They are a great bunch of folks to deal with.
We have also structured our site so that all the links on a page may in fact come from different web servers in our server farm. The main request is handled by the server that holds the session, but things like images etc get load balanced across the servers.
You can also serialize your session objects and store the sessions in a DataBase. This will add a bunch of overhead, however, you will get the same session, no matter what server you hit.
Hope this helps
RIck
On Tuesday, August 5, 2003, at 07:25 AM, [EMAIL PROTECTED] wrote:
Sorry for being thick but Im a bit confused as to when you are doing
anything with the sessions? If I make a request to one server, then go on
to another for the next request, how does server 2 get my session from
server 1 without server 1 having had to persist the session to disk every
time any change is made to it?
Pete
"Angus Mezick" <[EMAIL PROTECTED]> 05/08/2003 15:11 Please respond to "Tomcat Users List"
To: "Tomcat Users List" <[EMAIL PROTECTED]> cc: Subject: RE: how to suppor 30000 concurrent users
Doesn't seem to have that much of an effect. I guess I should profile
it though. I don't want to use session persistence because then I would
need to use network session clustering. Session clustering is a
requirement for my app. I figure using a DB instead of memory to store
my sessions is better than sending 5 network connections to the other 5
of the 6 web servers with the session data that will only be valid to
ONE of those servers. Before tomcat we were using Iplanet 4.1 and the
cisco load balance we have SAID it could handle session affinity but it
didn't seem to be able to. So we went with a DB solution which, to me,
seems to be the more optimal solution. The DB also means I can have a
MUCH larger number of active sessions using my servers because I don't
have to worry about the sessions using all my memory. I just have to
worry about DB disk space but I had have 2 or 3 terabytes of disk while
only have 2 GB of memory. Seems to be an easy trade.
--Angus
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 9:40 AM To: Tomcat Users List Subject: RE: how to suppor 30000 concurrent users
Angus, doesnt using a shared jdbc based session manager slow the whole thing down a lot? Why dont you just use session persistence? Pete
--------------------------------------------------------------------- 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]
