G
Guest
I have some questions in regards to Session variables and IIS Recycling:
1. Does the IIS setting 'Shutdown worker process after being idle' affect
an
application's session variables?
Or is IIS checking that all sessions are done before shutting down the
worker processes?
2. Does the Recycle worker processes setting kill all session variables
of
any running session?
3. If I want to insure that my ASP.NET 2.0 application has a certain
timeout.
Is setting the timout values in the application sufficient, or are
there settings
in IIS that need to be set?
4. How does changing my Session store from InProc to SQL server in my
application, affect session Timeout? Would changing it allow us not to have
a timeout? (an infinite value?). Would that solve any loss of the
session variables due to process recycling, since the variables would
be in SQL tables and not in memory (inProc)?
Thanks in advance..
Ed
1. Does the IIS setting 'Shutdown worker process after being idle' affect
an
application's session variables?
Or is IIS checking that all sessions are done before shutting down the
worker processes?
2. Does the Recycle worker processes setting kill all session variables
of
any running session?
3. If I want to insure that my ASP.NET 2.0 application has a certain
timeout.
Is setting the timout values in the application sufficient, or are
there settings
in IIS that need to be set?
4. How does changing my Session store from InProc to SQL server in my
application, affect session Timeout? Would changing it allow us not to have
a timeout? (an infinite value?). Would that solve any loss of the
session variables due to process recycling, since the variables would
be in SQL tables and not in memory (inProc)?
Thanks in advance..
Ed