ASP.NET应用程序池关闭问题 [英] ASP.NET application pool shutdown problem

问题描述

有时，异常会导致应用程序池关闭。我手动启动它，但问题是如何在 IIS 7.0 （Windows Server 2008）中自动执行此行为。

解决方案

如果应用程序池死亡，则由该池提供的资源的下一个请求将自动重新启动。但是，如果您在应用程序池上启用了快速故障保护，并且该池会在故障间隔时间间隔指定的时间间隔内比最大故障属性指定的数字多出多次， em>属性，那么您将收到一个 503服务不可用消息。此时，您必须手动重新启动应用程序池。要解决此问题，请禁用应用程序池的快速故障保护，或尝试增加该时间段内的故障数量，然后确定根本原因。例外，终止应用程序池。

Sometimes an exception causes application pool to shutdown. I start it manually but the question is how can I automate this behavior in IIS 7.0 (Windows server 2008).

解决方案

If an application pool dies, the next request for a resource served by that pool will automatically restart it. If, however, you have rapid fail protection enabled on the app pool, and the pool dies more times than the number specified by the maximum failures property within the interval specified by the failure interval property, then you will receive a 503 Service Unavailable message. At this point, you will have to manually restart the app pool.

To work around this, either disable rapid fail protection for the app pool, or try increasing the number of faults within the time period, and then determine the root cause of the exceptions which are terminating the app pool.

这篇关于ASP.NET应用程序池关闭问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！