K
Kevin Frey
Hello,
I've been reading that ASP.NET serialises (ie. processes one at a time) HTTP
requests if two simultaneous requests need to access the same session state.
It also makes note that ASP.NET tries to reacquire a lock on the session
state every 1/2 second until the timeout is reached, and then it will
forcibly release the previous users lock and take the lock for itself.
What is this timeout figure?
One of our Session state values is a live object that represents a
connection to an application server (in the future we'll dispense with this
and instantiate-on-demand using a "lightweight" connection, but we can't
right now), and it looks very much like two requests are hitting our
"connection" object simultaneously, resulting in dodgy behaviour, exceptions
etc.
Since ASP.NET is meant to protect us from having to manage this ourself, I'm
wondering what the timeout is (at which point you lose the protection of
ASP.NET).
Even a ballpark figure would be appreciated - seconds, minutes, hours?
Thanks
Kevin
I've been reading that ASP.NET serialises (ie. processes one at a time) HTTP
requests if two simultaneous requests need to access the same session state.
It also makes note that ASP.NET tries to reacquire a lock on the session
state every 1/2 second until the timeout is reached, and then it will
forcibly release the previous users lock and take the lock for itself.
What is this timeout figure?
One of our Session state values is a live object that represents a
connection to an application server (in the future we'll dispense with this
and instantiate-on-demand using a "lightweight" connection, but we can't
right now), and it looks very much like two requests are hitting our
"connection" object simultaneously, resulting in dodgy behaviour, exceptions
etc.
Since ASP.NET is meant to protect us from having to manage this ourself, I'm
wondering what the timeout is (at which point you lose the protection of
ASP.NET).
Even a ballpark figure would be appreciated - seconds, minutes, hours?
Thanks
Kevin