resource protection in IIS

[John Wood]

I know this might be served better in the aspnet forum, but I'm not having
much luck with an answer there...

I have a couple of questions about asp.net hosted in IIS:

1. If my ASP.net application gets caught in an infinite loop... how does the
process ever get terminated? Does it time-out and get forced to terminate?

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

[Nicholas Paldino [.NET/C# MVP]]

John,

If it is caught in an infinite loop, the client will eventually time
out, but the server will probably just keep processing along.

As for consuming all resources, there is a setting in ASP.NET which
indicates when the ASP.NET process should be restarted. The trigger for
this is a percentage of the total memory consumed on the machine. I think
that by default, it is at 60%, and you can change this in the .config file
for the app.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"John Wood" <sp**@isannoying.com> wrote in message
news:Om**************@TK2MSFTNGP12.phx.gbl...

I know this might be served better in the aspnet forum, but I'm not having
much luck with an answer there...

I have a couple of questions about asp.net hosted in IIS:

1. If my ASP.net application gets caught in an infinite loop... how does the process ever get terminated? Does it time-out and get forced to terminate?

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

[John Wood]

So when you rebuild the application that's running on IIS, does it kill off
any existing processes started by that application?

I mean, when you're developing you're sure to hit points where your app
hangs... just wondering if they ever get terminated!

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:ew*************@TK2MSFTNGP12.phx.gbl...

John,

If it is caught in an infinite loop, the client will eventually time
out, but the server will probably just keep processing along.

As for consuming all resources, there is a setting in ASP.NET which
indicates when the ASP.NET process should be restarted. The trigger for
this is a percentage of the total memory consumed on the machine. I think
that by default, it is at 60%, and you can change this in the .config file
for the app.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"John Wood" <sp**@isannoying.com> wrote in message
news:Om**************@TK2MSFTNGP12.phx.gbl...

I know this might be served better in the aspnet forum, but I'm not having much luck with an answer there...

I have a couple of questions about asp.net hosted in IIS:

1. If my ASP.net application gets caught in an infinite loop... how does

the

process ever get terminated? Does it time-out and get forced to terminate?
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

[Nicholas Paldino [.NET/C# MVP]]

John,

When you recompile your app, I believe that sessions that are currently
being serviced by ASP.NET will continue to be serviced by the old
assemblies. New sessions will use the new assemblies when you move them in.

As for the infinite loop detection, I don't believe that there is
anything that will detect this and shut it down automatically. You should
use a diagnostic tool if you feel this is happening to see how many long
running requests there are on your system.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"John Wood" <sp**@isannoying.com> wrote in message
news:u5**************@TK2MSFTNGP11.phx.gbl...

So when you rebuild the application that's running on IIS, does it kill off any existing processes started by that application?

I mean, when you're developing you're sure to hit points where your app
hangs... just wondering if they ever get terminated!

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:ew*************@TK2MSFTNGP12.phx.gbl...

John,

If it is caught in an infinite loop, the client will eventually time
out, but the server will probably just keep processing along.

As for consuming all resources, there is a setting in ASP.NET which
indicates when the ASP.NET process should be restarted. The trigger for
this is a percentage of the total memory consumed on the machine. I think

that by default, it is at 60%, and you can change this in the .config file for the app.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"John Wood" <sp**@isannoying.com> wrote in message
news:Om**************@TK2MSFTNGP12.phx.gbl...

I know this might be served better in the aspnet forum, but I'm not having much luck with an answer there...

I have a couple of questions about asp.net hosted in IIS:

1. If my ASP.net application gets caught in an infinite loop... how

does the

process ever get terminated? Does it time-out and get forced to terminate?
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

[John Wood]

Thanks Nicholas.

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:us**************@TK2MSFTNGP09.phx.gbl...

John,

When you recompile your app, I believe that sessions that are currently being serviced by ASP.NET will continue to be serviced by the old
assemblies. New sessions will use the new assemblies when you move them in.
As for the infinite loop detection, I don't believe that there is
anything that will detect this and shut it down automatically. You should
use a diagnostic tool if you feel this is happening to see how many long
running requests there are on your system.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"John Wood" <sp**@isannoying.com> wrote in message
news:u5**************@TK2MSFTNGP11.phx.gbl...

So when you rebuild the application that's running on IIS, does it kill

off

any existing processes started by that application?

I mean, when you're developing you're sure to hit points where your app
hangs... just wondering if they ever get terminated!

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote

in

message news:ew*************@TK2MSFTNGP12.phx.gbl...

John,

If it is caught in an infinite loop, the client will eventually time out, but the server will probably just keep processing along.

As for consuming all resources, there is a setting in ASP.NET which indicates when the ASP.NET process should be restarted. The trigger for this is a percentage of the total memory consumed on the machine. I think that by default, it is at 60%, and you can change this in the .config file for the app.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"John Wood" <sp**@isannoying.com> wrote in message
news:Om**************@TK2MSFTNGP12.phx.gbl...
> I know this might be served better in the aspnet forum, but I'm not

having

> much luck with an answer there...
>
> I have a couple of questions about asp.net hosted in IIS:
>
> 1. If my ASP.net application gets caught in an infinite loop... how does the
> process ever get terminated? Does it time-out and get forced to

terminate?

>
> 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
>
>