ASP Takes Over The Server

[Jim Heavey]

I have had a couple of instances where ASP.Net does not respond or I get a server is busy message. When I look at what is running on the server, I see the ASP.Net process consumming all of the CPU of the server. Memory usage seems to grow and grow and nevery drops. Since this is the very first application on the server that is an ASP.Net application, I am guessing that there must be some settings that I must need to adjust, but I am not at all sure what those setting might be

Any guidance on this subject?

[John Saunders]

"Jim Heavey" <an*******@discussions.microsoft.com> wrote in message
news:D9**********************************@microsof t.com...

I have had a couple of instances where ASP.Net does not respond or I get a

server is busy message. When I look at what is running on the server, I see
the ASP.Net process consumming all of the CPU of the server. Memory usage
seems to grow and grow and nevery drops. Since this is the very first
application on the server that is an ASP.Net application, I am guessing that
there must be some settings that I must need to adjust, but I am not at all
sure what those setting might be.

This is probably not a settings problem but rather an application problem.
You should find out what part of your application is taking up so much CPU
time.
--
John Saunders
johnwsaundersiii at hotmail

[Jim Heavey]

This occuring when no one is on the application, it is like some sort of run away process. It occured over the holiday weekend an it ran for 3 days straight just sucking up all of the resources. How could this be an application issue?

[John Saunders]

"Jim Heavey" <an*******@discussions.microsoft.com> wrote in message
news:CE**********************************@microsof t.com...

This occuring when no one is on the application, it is like some sort of

run away process. It occured over the holiday weekend an it ran for 3 days
straight just sucking up all of the resources. How could this be an
application issue?

The aspnet_wp process primarily handles requests and responses. Chances are
that any of its behavior, including misbehavior, is caused by requests or
responses, or both.

I suggest checking the IIS logs and system event logs. You'll also want to
try to find out when this problem starts, so I suggest adding a performance
alert for high cpu usage.
--
John Saunders
johnwsaundersiii at hotmail