由于以下原因，ISAPI报告自己不健康：“检测到死锁”。 [英] ISAPI reported itself as unhealthy for the following reason: 'Deadlock detected'.

问题描述

大家好，



昨天，当用户数量（负载）增加时，我们的生产服务器上遇到一个奇怪的例外（大约200多个用户） ）。



在事件查看器中部署web服务的Web服务器上的异常消息 - 应用程序日志部分：



ISAPI'c：\ winnt \microsoft.net \ framework \v4.0.30319 \ aspnet_isapi.dll'由于以下原因报告为不健康：'检测到死锁'。



浏览谷歌博客后，我们相信它可能是App Pool上的一些线程问题。不知何故，IIS 6中的线程池是gettign full并抛出异常。我们在UAT / SIT环境中没有遇到同样的错误。

但是，有些博客会产生误导并造成混淆。



如果任何人都遇到了上述异常，请分享上述例外的真正根本原因和解决方案。



Workaroudns尝试过：

1.重新启动网络服务器。

2.重置IIS。

3.重新安装新应用程序池（但要弄清楚）。



如何增加IIS 6中的线程池容量？还是其他任何解决方法？





请提前帮助和致谢!!



谢谢，Tapas

快乐编码

Hi All,

Yesterday we encountered a strange exception on our Production server when the number of the users were (Load) was getting increased (Approx 200+ users).

Exception message on the web server where the webservice is deployed in event viewer - application logs section:

ISAPI 'c:\winnt\microsoft.net\framework\v4.0.30319\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

After going through the blogs on google, we belive it could be some threading issue on the App Pool. Somehow, the thread pool in the IIS 6 is gettign full and throwing exceptions. WE did not experience the same error in UAT / SIT environments.
However, some of the blogs are misleading and creating confusions.

If anyone has encountered the above exception, please share the real root cause and solution for the aforemetioned exception.

Workaroudns tried:
1. Rebooting the web server.
2. Reset IIS.
3. reating new App Pool (Yet to figure out).

How to increase the thread pool capacity in IIS 6? Or any other workaround?


Please Help and Thanks in advance !!

Thanks, Tapas
"Happy Coding"

推荐答案

这篇关于由于以下原因，ISAPI报告自己不健康：“检测到死锁”。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！