DeadLock Issues

10 Apr 2007 4:38 PM

Duncan

Hi all,

We are running on W2K3, 64 bit, IIS6.. and recently started getting the
following..

ISAPI 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll'
reported itself as unhealthy for the following reason: 'Deadlock detected'.

The worst part is what follows..
1. Application pool creates a new worker process and tried to shutdown the
old worker process.
2. The old worker process fails to shutdown
3. The new worker process fails with the same deadlock issue.
4. Eventually, we have approx 20 worker processors and all memory is
consumed or aspnet fails.
5. The old worker processors can not be killed and the server must be
rebooted.

It is extremely annoying to have to end up rebooting a server but nothing we
have done enables us to remove/kill the w3wp's.

1. How can we find out what is causing the deadlock?
2. Why would a deadlock result in the issues we are experiencing and end
with a server reboot?

Thanks.

11 Apr 2007 8:05 AM

Laura T.

If you are very lucky, this might apply
http://support.microsoft.com/default.aspx?scid=kb;en-us;921217&sd=rss&spid=8291 ?

Otherwise, I'd check first all the possible logs/eventlogs and whatever to
see if the symptoms lead to something known (support.microsoft.com is a good
start).

If not, some good dumps and WinDGB may reveal the cause.
Here some pointers:

http://blogs.msdn.com/tess/archive/2006/02/23/537681.aspx
http://support.microsoft.com/?scid=kb%3Ben-us%3B828222&x=14&y=16
http://msdn2.microsoft.com/en-us/library/ms954590.aspx

Show quote

"Duncan" <Dun***@discussions.microsoft.com> ha scritto nel messaggio
news:2D6A60A2-0325-44DF-A628-FF8093FF16D4@microsoft.com...
> Hi all,
>
> We are running on W2K3, 64 bit, IIS6.. and recently started getting the
> following..
>
> ISAPI 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll'
> reported itself as unhealthy for the following reason: 'Deadlock
> detected'.
>
> The worst part is what follows..
> 1. Application pool creates a new worker process and tried to shutdown the
> old worker process.
> 2. The old worker process fails to shutdown
> 3. The new worker process fails with the same deadlock issue.
> 4. Eventually, we have approx 20 worker processors and all memory is
> consumed or aspnet fails.
> 5. The old worker processors can not be killed and the server must be
> rebooted.
>
> It is extremely annoying to have to end up rebooting a server but nothing
> we
> have done enables us to remove/kill the w3wp's.
>
> 1. How can we find out what is causing the deadlock?
> 2. Why would a deadlock result in the issues we are experiencing and end
> with a server reboot?
>
> Thanks.
>
>