Scott Hanselman

ASP.NET "Deadlock detected"

August 23, '04 Comments [0] Posted in ASP.NET
Sponsored By

On a private mailing list Richard Hundhausen dug up this good info if you've ever experienced the "Deadlock detected" error in ASP.NET, perhaps when calling a long running Web Service:

  • KB 821268 http://support.microsoft.com/default.aspx?scid=kb;en-us;821268
  • KB 828222 http://support.microsoft.com/?ID=828222
  • This reply from David Wang (MSFT) on the Google groups with some interesting information:

    You need to turn pinging back on. Report unhealthy depends on failing the ping (and failing the ping is what triggers IIS to recycle the worker process). Enabling pinging should not affect your other recycling options, since all you needed to do was turn off all the time-based recycling metrics -- from a default installation, all you need to turn off are "Idle Timeout" (15 minutes by default) and "Periodic Recycling" (29 hours by default).

    Regarding - responseRestartDeadlockInterval and responseDeadlockInterval -- there isn't anything comparable in IIS6 because ASP.Net is using the "report unhealthy" mechanism to get IIS6 to recycle itself. How the interval is configured should be specific to ASP.Net.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.