Hi,
For a busy production site, generally the application pool idle shutdown
setting will not affect session state since there are always new requests
come in and *ping* the worker process.
Actually the idle auto shutting down function is very important on server
health because application pool can have multiple worker process instance
in IIS 6.0 worker process mode. Based on these new health/recycling
features of application pool, sometime web applications with small
flaws(e.g occasional memory leak, deadlock, etc) can still *work* on IIS6
but will fail on IIS 5.x or eariler.
In this specific case, I'd suggest you adjust the idle shutdown time to a
value greater than 4 hours instead of disabling it.
Please let me know if you have more concern on this.
Thanks.
Sincerely,
WenJun Zhang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.