IIS 6.0 应用程序池崩溃 [英] IIS 6.0 Application Pool crash

问题描述

在生产服务器上有很多麻烦.某些路由导致应用程序池崩溃，事件 id 为 1011:

Have a lot of troubles on production server. Some routing cause crashing of Application Pool with event id 1011:

事件类型:警告事件来源:W3SVC事件类别:无事件编号:1011日期:2009 年 1 月 21 日时间:上午 9:08:17用户:不适用电脑:xxxxxxxxxxxx说明:

Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1011 Date: 1/21/2009 Time: 9:08:17 AM User: N/A Computer: xxxxxxxxxxxxx Description:

为应用程序池DefaultAppPool"提供服务的进程与万维网发布服务发生了致命的通信错误.进程 ID 为3788".数据字段包含错误号.8007006d

A process serving application pool 'DefaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '3788'. The data field contains the error number. 8007006d

在我发现问题之前，我有几个小时非常辛苦.感谢 Tess Ferrandez 和她的 博文 我找到了.

I have a few very hard hours for me before I found a problem. Thanks to Tess Ferrandez and her blog post I found it.

始终仔细检查您在 asp.net 应用程序中的多线程代码.当发生未处理的异常时，应用程序池崩溃并且很难找到原因.

Always double check Your multithreaded code in asp.net application. When Unhandled exceptions occurs application pool crashes and it's damn hard to find WHY.

推荐答案

Tess 的博客对我来说有点高级.在找到帮助我调试转储文件的正确文章之前，我不得不四处搜索.本文将帮助其他想要调试崩溃的 asp.net 应用程序池的人但不知道如何开始.

Tess's blog was a little advanced for me. I had to search around for quite a bit before I found the right articles that helped me debug my dump files. This article will help others who want to debug their crashing asp.net application pools but don't know how to start.

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