This can be caused by many things, in code its typically threading problems,
web service calls etc overloading the worker processes, recursive routines
not releasing resources like connections and forcing the app pool to recycle
because of a deadlocked state ie. it has too many threads waiting for
connections to terminate and become available that it thinks its unhealthy.
If your load testing, this is the first place I would look.
Read these and see if it helps you understand the root cause of your problem
better:
http://msdn.microsoft.com/msdnmag/is...s/default.aspx http://msdn.microsoft.com/library/de...netchapt06.asp
Regards
John Timney (MVP)
"A.J" <aj********@gmail.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
Hi,
We are usiing IIS 6. and running a load test(8hours) for our
application.Our last run failed and the event log shows the following:
System Log:
A process serving application pool 'DefaultAppPool' exceeded time
limits during shut down. The process id was '2860'.
Application Log:
ISAPI 'C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspn et_isapi.dll'
reported itself as unhealthy for the following reason: 'Deadlock
detected'.
This is the first time we are getting this type of error.
perfmon is showing w3wp processor time inc. constantly.
but its working set is fine.
Could u please help me out!!!
regards,
Ajay
