« Previous Next »

Answered Thread: Server.Transfer

Last post 11-07-2009 1:45 AM by StephenHoe. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 11-02-2009, 12:47 PM

    Server.Transfer

    Does Server.Transfer guarantee not to redirect to a different physical server in a web farm load balanced environment?
    If "InProc" mode is used for session along with Server.Transfer there should be no issue in a web farm?

    Thanks
    Stephen

  • 11-07-2009, 1:00 AM In reply to

    Answered Re: Server.Transfer

    Hi,

    Server.Transfer simply changes the "focus" on the Web server and transfers the request instead of telling the browser to redirect. This means there is no new request to the web farm when using Server.Transfer. Hence, it should not redirected to a different physical server.

    If you are using "InProc" mode with web farm, you may encounter some issue (session lost etc.). This is because the different requests may been forward to different physical server. Below is an article about Affinity in the NLB, hope helps:

    Preserving Session State in Network Load Balancing Web Server Clusters
    http://technet.microsoft.com/en-us/library/cc781149(WS.10).aspx

    Leo Tang
    Microsoft Online Community Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
  • 11-07-2009, 1:45 AM In reply to

    Re: Server.Transfer

    So, if throughout the user session all the communication between pages are being handled by Server.Transfer then "InProc" mode should not lose any session in a web farm NLB enironment.

    The reason for this is we are experenicing scalability issue with using SQLServer as session state.  We have a very high traffic application (40 million+ users) and using SQLServer as the session DB is creating a lot of unexpected I/O.  Can't afford to scale out the DB just for the session data purpose and need to find a solution.

     Thanks

Page 1 of 1 (3 items)
Microsoft Communities