Not a fix, but if you want to maintain Session State when the process recycles, you can use out-of-process Session State. Since this maintains the Session in a seperate process, the user should experience less disruption when aspnet_wp.exe gets killed. Allen
-----Original Message----- From: Sills, Adam [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 8:20 AM To: [EMAIL PROTECTED] Subject: [DOTNET] aspnet_wp.exe recycling Has anyone else experienced the aspnet_wp.exe process recycling excessively? On one server that gets very little usage (2-5 users a day, and only a few hours of real use, but it does a whole lot) the process never deadlocks and never recycles itself. On another server, with another large application, and roughly 2000 unique visitors a day (each person staying for 30-60 minutes) the aspnet_wp process dies almost hourly. Sometimes more than once per hour, but it's been incredibly consistent... During downtimes (2-7am EST) the process is fine as it barely gets any use (it only seems to recyle every 4 hours). Is this directly due to something I'm doing? Or is there something else going on here I don't know about? TIA, Adam.. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
