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

问题描述

我们的 ASP.NET 2 Web 应用程序非常优雅地处理异常.我们在 Application_Error 中捕获 Global AAX 中的异常.从那里我们记录异常并向用户显示一条友好的消息.

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.

然而，今天早上我们部署了我们网站的最新版本.它运行了半小时，但随后应用程序池崩溃了.在我们恢复之前的版本之前，该站点没有恢复.

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屋！