We are haveing more and more OutOfMeomoryException these days, at first, it happened once a week, now three times a week. The worst thing is, IIS didn't recycle its aspnet_wp.exe thread when this exception was thrown. And every one tried to connect IIS server now saw this error.
Our configuration is as follow,
Windows server 2000,
2 Xeon CPU
3.7GB free space on system drive, and much more on other drives
IIS 5.0 with net framework v1.0.3705 and v1.1.4322.573 installed
All the web applications are configurated to run with .net framework v1.1.4322.573
Average daily page views is about 100,000, all the isolation level are set to medium.
MemoryLimit in all web.config files are set to default value at 60 percent. The consumed memory of aspnet_wp.exe was at only 600MB as the OutOfMemoryException happened, much lower than 2GB*605 = 1.2GB. I read quite a few threads on line, some said that the MemoryLimit of .net framework 1.0 should be set to no more than 800MB if not with /3GB switched on. But I found no article to confirm whether this also appliest to .net framework 1.1. Could anyone explain it for me?
I also recognized that Microsoft admiitted there is a bug in .net framework 1.1 which would report OutOfMemoryException when there is pretty much memory available, the hot fix was bundled in .net framework 1.1 SP1. However, in my situation because it is a production system used by hundreds of people, we dare not to apply such a big change without concrete evidence.
My question is what should I do, I mean to change the IIS settings, or settings in web.config files, to minimize impact of this OutOtMemoryExceptions? I guess it would also be acceptable, if IIS recycle its aspnet_wp.exe thread when it goes out of memory rather than refuse any more connection.
Any advice is appreciated.