w3wp process 100%....

[ahmnasa]

Hi all,

OK so I have windows 2003 server that's has been running for over 2 years now without a problem. I have over 20 ASP.NET and ASP 3.0 websites running on it with most using the SQL Server Database on the server.

Now all of a sudden IIS (w3wp.exe) has started to go to 100% CPU or try to for no apparent reason. I restarted the server but it still does it. I restarted the IIS Services and w3wp disappears but as soon as I click "Play/Run" on any website (ASP.NET or ASP or just HTML website) it goes to 100% straight away.

I have no idea how to fix it and as I've mentioned before, i have over 20 websites offline right now and I really need some help.


Here are a few entries in the Event Log that I seen:

2 of: "A process serving application pool 'DefaultAppPool' exceeded time limits during shut down. The process id was '1364'. "

Many of: "The WinHTTP Web Proxy Auto-Discovery Service has been idle for 15 minutes, it will be shut down."
and
"The WinHTTP Web Proxy Auto-Discovery Service suspended operation."

also:

"ISAPI 'c:\windows\microsoft.net\framework\v2.0.50727\asp net_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'."


Any help would be greatly appreciated.

Thanks
Ahm

[bartonc]

I found this from an expert named David Wang:

IIS6 has several features to help with this situation.

First thing you want to do is isolate your dev environment from the
production environment. This is best done using Application Pools. Create
and use a custom Application Pool when developing your code, and let the
rest run as production.

This allows you to do the following when you screw up code that runs in
w3wp.exe -- you can now RECYCLE the custom Application Pool running your dev
code WITHOUT affecting production code running in the other Application
Pools. The recycle will kill all the misbehaving w3wp.exe of the recycled
Application Pool.

Thus, if the w3wp.exe running your dev code has an infinite loop, just
recycle your dev App Pool and things should go back to normal.

If you do not want to manually recycle, you can configure additional
CPU-monitoring health metric on the dev Application Pool to automatically
recycle the application pool after it has reached a certain CPU% over a
configurable period of time. In other words, it is possible for you to tell
IIS to automatically recycle your dev application pool if it has been 100%
CPU for one minute -- so you can just keep working and IIS6 will just
recycle automatically.

There are many other health-monitoring metrics on IIS6 that do similar
behavior, and you can experiment and take advantage of all of them on your
dev Application Pool.

The key is to first isolate your potentially badly-misbehaving dev
application in its own Application Pool. Then, you can put many IIS6
features to work for you.