The corporate answer is to buy JRun 3.0 Enterprise and use ClusterCats
(which is included in the Enterprise license) to do your load balancing and
fail over. ClusterCats also works nicely with Cisco LocalDirector if you
have that. As someone else said, no matter what, you'll need to turn on
sticky sessions to lock sessions to servers. Another alternative is to
maintain all session data on the server in a database, but I think this
would be much slower.
There are other folks here who know a lot more about ClusterCats and load
balancing issues than I do, so if you have any questions about it, fire
away.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: Earle Flynn [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 09, 2000 8:49 AM
> To: [EMAIL PROTECTED]
> Subject: Load Balancing and Session Var's
>
>
> All our java applications (servlets, JSP based) are run by
> JRUN and we
> use the JRUN session to save session data. But since our website is
> supported by two webservers with round-robin DNS load balancing, the
> user can get switched to the other webserver in the middle of
> a session
> and lose all the session data. Is there a solution for this.
> Is there a
> way to make the web-browser to the same physical webserver
> for the life-
> time of the web-browser session?
>
> Any pointers or help would be greatly appreciated.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
