Last post Jul 25, 2011 06:47 AM by GPankaj
Jul 22, 2011 05:21 PM|lakeshore|LINK
If you have physical load balancers (F5) configured to use sticky sessions in a three-tiered (web server, app server and database) or two-tied archtecture (web server/app server and database, what session management solution do you use?
1.InProcess on each app server in the web farm;
2.A seperate StateServer (outProcess) on a separate server; or
3.SQLServer (database based)
Jul 24, 2011 01:39 PM|XIII|LINK
I don't know specifically for F5 load balancers but all (infrastructure) architectures I've seen the last years which included sticky sessions kept using InProc session state management as it was the load balancer who decided that every recurring postback/page
request of an identified user was redirected to that same server.
Jul 25, 2011 06:47 AM|GPankaj|LINK
To avoid losing session you can enable the client affinity feature. It will ensure all TCP connection to be directed to the same cluster host. I think below articles are worth reading related to your query.
Hope this helps