Last post Nov 05, 2013 04:19 AM by AidyF
Nov 03, 2013 08:51 PM|rcx4009v2|LINK
We are currently having a problem with regards the session state of our web application when we access it thru F5 load balancer using the Alias of the IP. But when we access the application using the IP address, session variables are created.
For example, if we access the application using http://F5_IP_ALIAS/Web_Application the application can't create session variables and thus when we access the session variables we encounter the error: Object reference not set to an instance of an object.
But if we access the application using http://10.30.50.101/Web_Application the application is working properly and able to create and access session variables.
Anyone have an Idea what is wrong with the application? or is this an issue in F5 Load Balancer?
Nov 04, 2013 04:43 AM|AidyF|LINK
Are you using sticky sessions? If your session variable are just being lost, I'd look into how the load balancer is handling cookies. Is it removing the asp.net session cookie for example, or altering their values in some way. Cookies are the key to sessions
retaining their value for your clients so I'm fairly sure the problem will be in that area.
Nov 04, 2013 09:47 PM|rcx4009v2|LINK
Thanks for the reply. I'm not really sure if they configured the load balancer to use sticky sessions. But I bet it is not using sticky sessions. Though the current session configuration we are using in the application is to use a Session State server. Do
we still need to use sticky sessions if we are already using a Session State server?
Nov 05, 2013 04:19 AM|AidyF|LINK
If you're using state server then you don't need sticky sessions. You still need the session cookies to remain intact though. It's something you'll need to start looking at at a network level. Do some packet sniffing or use fiddler to examine the traffic
going through the load balanacer vs going to the server direct and see if you can see anything obviously different with the cookies.