This process doesn't shut down the server, what it does is shut down the
worker processes that are running under the application pool that hit
its maximum. Also the help file says that the application pool "shuts
down and resets" so I believe what happens is the existing individual
worker processes stop accepting requests, try to complete their current
work (dying off if they can't before the time limit is up), the
application pool shuts down, then the application pool comes back up and
starts handling requests again. Do note, if you don't create new
application pools to run each of your web applications in (e.g. you
leave them all in the default) you will see behavior similar to shutting
down the entire server, however if you isolate your web apps into
separate application pools only the mis-behaving web app will shut down
while the others go along their way uninhibited. Hope that helps.
John M Deal, MCP
Necessity Software
Aaron wrote:
WOW! I didn't know IIS 6 has this feature built-in. You saved the day John.
i have a question about
action performed if exceeds max cpu use: if i choose shutdown would it also
restart the server?
is it better to have more worker processes?
"John M Deal" <jo******@necessitysoftware.com> wrote in message
news:OK**************@TK2MSFTNGP15.phx.gbl...
If you are using IIS6 you can do this by configuring the application pool
that the website runs under. Simply bring up the application pool
properties page in its MMC and select the Performance tab and set the
appropriate values. It is pretty self explanatory but there is a help
page available for each of the settings. Hope this helps.
Have A Better One!
John M Deal, MCP
Necessity Software
Aaron wrote:
how do i write a script like this?
if dllhost.exe's cpu usage is greater than 90% then
run iisreset
end if
Thanks in advance,
Aaron
