Debugging ASP.NET Session State server issues
Posted
by Cleggy
on Stack Overflow
See other posts from Stack Overflow
or by Cleggy
Published on 2009-01-19T00:31:08Z
Indexed on
2010/06/14
13:52 UTC
Read the original article
Hit count: 252
We have an application that runs over load balanced server instances, and therefore is configured to use the ASP.NET session state service, which is running on one of our DB servers. While both instances of our app can successfully connect to the state server, changes in session state data are not being reflected across both of them. FI, If I call Session.Add('SomeKey', SomeData)
on Server A, this is not being reflected if I then try to access Session['SomeKey']
on Server B.
Session.SessionID returns the same value on both servers, and I have checked that they are both using the same validationkey and decryptionkey values configured in the machinekey section of machine.config. I even tried specifying these values in the apps web.config.
What other things should I be looking out for which may be causing these symptoms, and what steps can people recommend to help debug this issue?
© Stack Overflow or respective owner