How should I debug a vb.net website in iis6 that is throwing 'Deadlock detected' errors and becomes
Posted
by jskunkle
on Server Fault
See other posts from Server Fault
or by jskunkle
Published on 2010-05-25T13:43:38Z
Indexed on
2010/05/25
13:51 UTC
Read the original article
Hit count: 393
A few times a day, our vb.net (IIS 6.0) website is randomly throwing the following error and becomes completely unavailable for 5-15 minutes at a time while the application is recycled:
ISAPI 'c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.
The website ran for months on the exact same server in beta without problem - but the problem started over the weekend when we made the site live. The live site is under some load but less than many of our other production websites.
How should I attack this problem? I've looked into orphaning the worker process and creating a dump file - but I'm not sure how to analyze that. Any advice or information is appreciated. Thanks, Shane
© Server Fault or respective owner