There is a problem with load balancing and using session variables. Each
request from the same user may get directed to a different webserver.
Since session variables are local to the webserver itself, a first request
going to one webserver may set a session variable. A second request from the
same user may go to another webserver. On the 2nd webserver, that session
variable doesn't even exist. In fact, that session doesn't even exist (using
the APSESSION cookie).
In order to load balance you have a few options:
1) Rewrite the site so that it does not depend on session variables (use
cookies instead)
2) Configure the load balancer so that all requests from the same IP goes to
the same server. - Sometimes referred to as sticky
In addition to number 2, you will have to find all of AOL's proxy addresses
and send them ALL to the same server. The reason is that multiple requests
from an AOL user may (will) come from different IP addresses.
Number 2 requires a sophisticated load balancer. Number 1 requires more
development work. But solution 2 doesn't solve the problem if one of your
servers goes down. If that happens, users that were using that server get
pushed to the working server without their session variables.
"Jonathan Chong" <jo******@3exp.com> wrote in message
news:Od**************@tk2msftngp13.phx.gbl...
I have problem with AOL browser (IE and Netscape are OK) accessing my Web
site after putting up a load balancer that will go to W1 or W2.
The problem does not happen when there is only Web server and no load
balancer installed.
The problem is on the checking of the session timeout function. This
function will check if the session variable's value is missing. If it is
missing, it will direct to time out page.
How should I solve this problem.
