OK...here's the deal. I have an ASP .Net web app running on IIS6/Server 2003.
It's setup to run "out of process" and session state is currently being managed by Microsoft's ASP Net State Service.
Some users access this web based application via a published application on a Citrix server.
Some users report being "timed out" long before the application's 1 hour idle timeout. (If the app actually times you out you receive a popup message).
I've checked the IIS setting ans confirmed that the session state is enabled and that the session timeout is 61 minutes, 1 minute longer than the application's timeout.
I have verified that if the worker process is recycled the user is not kicked out of the application (session state is functioning as designed)
My question then is....if some users report that they are being asked to log back into the application LONG before the timeout period demands. Could the session information be "confused" since there are multiple sessions originating from the same "client" (Citrix server), same IP? Could user X's session be eliminated because user Y's session was idle for more than 61 minutes?
I am basically wondering how sessions are handled. What makes them unique? Machine name? IP? Something else?
I am new to out of process and session state so please excuse my ignorance.
Thanks in advance.
Jason
-- Jason
"It's Just Ones and Zeros
It's setup to run "out of process" and session state is currently being managed by Microsoft's ASP Net State Service.
Some users access this web based application via a published application on a Citrix server.
Some users report being "timed out" long before the application's 1 hour idle timeout. (If the app actually times you out you receive a popup message).
I've checked the IIS setting ans confirmed that the session state is enabled and that the session timeout is 61 minutes, 1 minute longer than the application's timeout.
I have verified that if the worker process is recycled the user is not kicked out of the application (session state is functioning as designed)
My question then is....if some users report that they are being asked to log back into the application LONG before the timeout period demands. Could the session information be "confused" since there are multiple sessions originating from the same "client" (Citrix server), same IP? Could user X's session be eliminated because user Y's session was idle for more than 61 minutes?
I am basically wondering how sessions are handled. What makes them unique? Machine name? IP? Something else?
I am new to out of process and session state so please excuse my ignorance.
Thanks in advance.
Jason
-- Jason
"It's Just Ones and Zeros