64-bit Editions of IIS
IIS in SySWoW Mode
Last post Apr 05, 2008 10:58 AM by PawelPabich
Mar 17, 2008 03:44 PM|LINK
Mar 18, 2008 06:23 PM|LINK
You can configure the application pool to orphan the worker process rather than kill it when this condition happens - you can then use
adplus to collect a hang dump of the worker process which can be analyzed to figure out what in the process is deadlocked.
Apr 04, 2008 03:10 PM|LINK
Is there any document that describes what ASP.NET means by " reported itself as unhealthy for the following reason: 'Deadlock detected'"? I would like to know how it decides if it's dead locked or not?
Apr 04, 2008 09:26 PM|LINK
It means that the asp.net thrads have not returned from whatever activity they were doing for a very long time and asp.net has run out of threads - this would normally indicate deadlock. This
kb also talks about how to generate dumps for analysis for this condition.
Apr 05, 2008 10:58 AM|LINK
Thanks for quick response. What do you mean by very long time, is is configured somewhere?
I've tried before the article you mentioned but IIS recycled the process and didn't create any dump. I suppose my only option is to run adplus in crash mode even though it affects performance. Do you have any other ideas where to look to find more information?