Pool application in IIS 6

I have difficulties to tweak the pool application in IIS 6. I try to improve the performances of my different websites.

Most of the time, when I get a lot of requests, the worker process stall with a CPU use of 98%.
So I was quite confident that setting a pool with a CPU monitoring could sove the problem.

Nope, it's worst becuase if I activate this feature, I end up with a lot of Service Unavailable from IIS.

By the way, does somebody knows how to create a custom error page for this kind of behavior ? It's not managed by IIS as a typical 500 server error, so I am not sure how to handle this.

 

2 Comments

  • I've seen the service unavailable and it's an ASP.NET error (use the customErrors section in web.config) rather than an IIS error and can occur whilst a process is restarting. We found on Windows 2003 we had an issue with Appdomains continually recycling. A MS Hotfix provided a work around (although I can't currently find it). You could also try assigning multiple physical processes in the App Pool properties (so one can be recycled whilst the other is still servicing requests).

  • There are couple service unavailable errors, one is coming from Asp.Net (when its request queue fills up or when a request times out, either running or in the queue) and the other is from IIS, when IIS' request queue fills up. the first one should be changable in web.config (or machine.config if you want to do it machine-wide) the second is set in IIS' metabase, it's an error 500.13 (why Microsoft didn't use the standard 503 is beyond me).

Comments have been disabled for this content.