Forum Discussion
NimbostratusPersistance session Idle time out issue
Hi, We have a web application deployed to multiple servers running in IIS 7.5 windows server 2008r2, they have same configuration and all the trafic is directed by Big-IP load balancer.
The IIS app pool setting of idle timeout and web application session state timeout are set to 35 minutes. All the server have the same semettings. We have a timeout page that displays timeout error when user idle time is reached to 35 minutes.
User are getting runtime error because the app pool is timed out prior session timed out, we reproduced this error in our test environment by setting app pool idle timeout value to shorter time than applicaiton session state timeout value.
I am suspect that Big-IP has an persistance session idle timeout setting that has timed out user session. If my assumption is correct, could you tell me how to configure it to a custom value?
Thanks
2 Replies
Sorin_86551You can create a new persistence profile going to "Local Traffic -> Profile -> Persistence". After creating the new profile you will be able to edit the timeout values. Or just edit the timeout values on your current profile. What kind of persistent profile are you using ?
- Kevin_Stewart
Employee
A persistence profile can have a timeout value, and many of them do have fairly short idle timeouts. If persistence was the problem, users would potentially get re-load balanced to other servers in the pool. What kind of persistence are you using now?
Otherwise, keep in mind that the TCP session that a client maintains with the BIG-IP (proxy) is not the same TCP session that the BIG-IP maintains with the server. Anything that happens at layer 7 though (ie. HTTP) is generally between the client and server directly.
