我如何崩溃的应用程序池？ [英] How do I crash the App Pool?

问题描述

我们的ASP.NET 2.0 Web应用程序处理异常非常典雅。我们赶在全球的Application_Error ASAX例外。从那里，我们记录异常和我们展示一个友好的信息给用户。

Our ASP.NET 2 web application handles exceptions very elegantly. We catch exceptions in Global ASAX in Application_Error. From there we log the exception and we show a friendly message to the user.

不过，今天早上我们部署了最新版本的网站。它跑OK了半个多小时，但随后的应用程序池崩溃。该网站没有回来，直到我们恢复了previous发布。

However, this morning we deployed the latest version of our site. It ran ok for half an hour, but then the App Pool crashed. The site did not come back up until we restored the previous release.

我怎样才能让应用程序池崩溃，并跳过正常的异常处理程序？我试图复制这一问题，但至今没有运气。

How can I make the app pool crash and skip the normal exception handler? I'm trying to replicate this problem, but with no luck so far.

更新：我们找到了解决办法。我们的一个网页被屏幕抓取另一页。但是URL配置不正确，并在页面结束了屏幕抓取的本身的无限，从而导致堆栈溢出异常。

Update: we found the solution. One of our pages was screenscraping another page. But the URL was configured incorrectly and the page ended up screenscraping itself infinitely, thus causing a stack overflow exception.

推荐答案

最常见的错误，我有看到和池撞车是循环调用。

The most common error that I have see and "pool crash" is the loop call.

public string sMyText
{
   get {return sMyText;}
   set {sMyText = value;}
} 

只要打电话给sMyText ...

Just call the sMyText...

这篇关于我如何崩溃的应用程序池？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！