This depends largely on what version of IIS you are running. IIS5, it will
take down the process since there is no true isolation mode. IIS6 achieves
true isolation so strained resources only affect the particular application
pool. Note that high cpu will affect the server since it is necessarily a
shared resource. IIS6 allows for the recycling of the application pool based
on particular settings so it is possible to protect other application pools
--
Regards,
Alvin Bruney
[ASP.NET MVP
http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here...
http://tinyurl.com/27cok
"John Wood" <sp**@isannoying.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
I have a couple of questions (that may be more IIS related):
1. If my ASP.net application gets caught in an infinite loop... how does
the
process ever get terminated? Does it time out?
2. If my ASP.net application consumes all resources (eg. creates a bunch
of
brushes it doesn't release), can this affect other processes running on
the
ASP server at my hosting site?
Thanks,
John