On 18-8-2009 16:34, Johan Duflost wrote:
Hello,Here is an excerpt of our config file : appsession ASP.NET_SessionId len 52 timeout 1h cookie ASP.NET_SessionId prefix option persist balance roundrobin option forwardfor option httpclose server 1 xx.xx.xx.xx:80 cookie 1 check inter 3000 rise 2 fall 3 server 2 xx.xx.xx.xx:80 cookie 2 check inter 3000 rise 2 fall 3 server 3 xx.xx.xx.xx:80 cookie 3 check inter 3000 rise 2 fall 3 Did you see anything special that could explain this behavior?
Well, to my best knowledge (but please correct me if I'm wrong), the 'cookie' option make sure you have session stickyness.
With session stickyness, you don't have perfect balancing, since, well.. users stick around :-) Some user's sessions take 10 seconds, others will take 10 minutes, and only new users (which) don't have a cookie will be round-robin sent to a new server.
If you do want perfect balancing, you have to turn off stickyness. But that might mean you have to adapt your ASP.NET application to non-sticky sessions (if you need server-side user sessions, you'll have to do something like storing the sessions in a central db, and identifying users by cookies or something like that, like all big players do).
-- With kind regards, Angelo Höngens systems administrator MCSE on Windows 2003 MCSE on Windows 2000 MS Small Business Specialist ------------------------------------------ NetMatch tourism internet software solutions Ringbaan Oost 2b 5013 CA Tilburg +31 (0)13 5811088 +31 (0)13 5821239 [email protected] www.netmatch.nl ------------------------------------------
