|
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Application Center NLB Session handling
<i><b>Originally posted by : Joe (jkusky@zaxit.com)</b></i><br />I wanted to give anyone considering App Center a heads-up on a potential problem:<br /><br />If you need to hold session state in your apps , and you are using NLB, read on!<br /><br /><br />Through the use of Single Affinity NLB will hold session state. What most people don't know is that the session is never dropped. (This is not to be confused with the webservers session timeout) When a user first logs onto a server through the VIP NLB directs the user to one of the available servers, and opens a session. From that point on the user will continue to hit the same server unless it is down, or the cluster is broken. Effectively balancing the load on the users first initial login, but never there after.
|
|
#2
|
|||
|
|||
|
Hi Steve,
According to MS documentation NLB does not hold session state, I tend to beleive you more than them as you have actually used it :-) Could you please confirm that once a client has connected to a server in the cluster that they will remain with that until their ASP session expires or is lost? I don't want to have to maintain state outside of the web server as MS suggest (link below). http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/ecommerce/deploy/rollout/duwwsr.asp Look forward to hearing from you Thanks ~ben |
![]() |
| Viewing: ASP Free Forums > System Administration > Microsoft IIS > Application Center NLB Session handling |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|