We are having some issues with our .NET web applications. Every so
often a computer will peg its CPU at 100% for some period of time. I am
told anywhere between 30mins and 2 hours. I have seen some kb articles
about asp_wp and 100% but I do not believe that is our issues. I am
fairly certain that the probelm is caused by one of the applications
running on the server. Ok so here are the questions.
Are there any perfmons that can be used to determine which asp.net app
is causing the cpu to spike up?
Is there any code that can be written to see what is happening?
What I am trying to accomplish is to determine the offending
application. What toold exist?
Thanks
RichHi Rich
As for the 100% cpu and troubleshooting on multi-web app server problem.
There are different options which depend on the server's OS version. Is
your webserver win2k server or win2003 server?
If you're using the Win2k server, since the processModel are the fixed
isolation mode. All the web application shared the same workerprocess.
There hasn't any buildin means or tools to determine which app caues the
problem. We have to test them one by one.
However , on win2k3 box, the IIS6 has provided a new workerprocess
isolation model( application pool model) which can let use isolate each web
application in a separate workproesss. You can have a look at the following
reference discussing on this:
#Chapter 20 C Hosting Multiple Web Applications
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/thcmch20.asp
Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Thanks for the feedback. This is a W2K server hosting these
applications. So I am left with the testing of individual applications.
Would this testing be done in a traditional manner (ie click and watch)?
If so I was hoping for something a little more than that. Any other
ideas? Thanks
Rich
In article <9LvS$c4eEHA.1600@.cpmsftngxa06.phx.gbl>, you say...
> Hi Rich
> As for the 100% cpu and troubleshooting on multi-web app server problem.
> There are different options which depend on the server's OS version. Is
> your webserver win2k server or win2003 server?
> If you're using the Win2k server, since the processModel are the fixed
> isolation mode. All the web application shared the same workerprocess.
> There hasn't any buildin means or tools to determine which app caues the
> problem. We have to test them one by one.
> However , on win2k3 box, the IIS6 has provided a new workerprocess
> isolation model( application pool model) which can let use isolate each we
b
> application in a separate workproesss. You can have a look at the followin
g
> reference discussing on this:
> #Chapter 20 =3FC Hosting Multiple Web Applications
> http://msdn.microsoft.com/library/d...ft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>
>
>
Hi Rich,
Thanks for your followup. As for such problem, if you have found the web
application which cause the problem, I think you'd better continue to
narrow down the problem to some certain web pages or component which may be
the root cause. Also, you can have a check directly in the code logic to
see whether there is any potential issues. Currnetly there're any
particular tools focus on such problem.
In addition, if you still feel
on this issue, I recommend that yourequest a regular case on it since intensive troubleshooting(such as Dump
analyse) would be done quickly and effectively with direct assistance from
a Microsoft Support Professional through Microsoft Product Support
Services.
Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Thanks Steven. I was afraid there would be no way of tracking this
down. If we can't find the app we will contact MPS. Rich
In article <Cvm$ywefEHA.3212@.cpmsftngxa06.phx.gbl>, v-
schang@.online.microsoft.com says...
> Hi Rich,
> Thanks for your followup. As for such problem, if you have found the web
> application which cause the problem, I think you'd better continue to
> narrow down the problem to some certain web pages or component which may b
e
> the root cause. Also, you can have a check directly in the code logic to
> see whether there is any potential issues. Currnetly there're any
> particular tools focus on such problem.
> In addition, if you still feel
on this issue, I recommend that you
> request a regular case on it since intensive troubleshooting(such as Dump
> analyse) would be done quickly and effectively with direct assistance from
> a Microsoft Support Professional through Microsoft Product Support
> Services.
> Thanks.
>
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>
