| David Wang [Msft] 2005-06-28, 7:50 am |
| ASP stores session state inside in-process.
IIS6 Application Pool recycling will kill processes, thus destroying the
state stored in them (and hence cause prematurely expired sessions).
Thus, setting Session timeout in ASP is not sufficient. The Application Pool
must not have any parameters that cause it to recycle in less time.
Recycling can occur for a variety of reasons, all configurable for the
Application Pool. As well as crashes in your web application can cause
recycling.
Thus, from IIS perspective, everything is behaving as-configured,
by-design -- even if you are losing your sessions unexpectedly.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ted Bogucki" <ted@sma-promail.com> wrote in message
news:edm6zIzdFHA.4060@TK2MSFTNGP10.phx.gbl...
I have an asp application running on both iis5 and iis6. (not .net) The
server ruhnning IIS5 has no problem running my application. IIS6 randomly
times out WEB users. The session timeout is set for 60 minutes. I will
get timed out in iis6 in less than 5 minutes. Are there any other
settings that can be changed to stop this from happening
|