7

This is an issue I've had twice now over a couple of months. Basically I've gotten a call saying our site is giving an HTTP error 503, I take a look at the IIS7 Manager and notice the AppPool has switched itself off. I restart it and it continues happily on it's way until a few months latter it happens again.

The IIS manager is handling four sites, both times this issue occurred on the same site. The .NET Framework version being used is v4.0.

Looking at the event log I see the following

Web Server IIS:

Warning: Event 5011 "A Process serving the application pool 'foo' suffered a fatal communication error with the Windows Process Activation Service. The process id was 'X' The data field contains the error number." - This warning appears 5 times, with 5 difference values for X, this takes place over about a minute 10-15 seconds between each warning.

Error: Event 5002 "Application pool 'foo' is being automatically disabled due to a series of failures in the process(es) serving that application pool."

Application log:

Error: Event 1000: "Faulting application name: w3wp.exe, version 7.5.7601.17514, time stamp: 0x4ce7afa2.
Faulting module name: clr.dll version 4.0.30319.17929, times tamp: 0x4ffa59b1. Exception codeL 0x0000fd"

Information: Event 1001 "Fault bucket, type 0
Event Name: APPCRASH Response: Not available"

The above two events occur over the same time period, first the error followed by two information events. This occurs five times and lines up with the warnings from the web server log.

If anyone can clarify what is going on it would be much appreciated. I'd rather not be worrying that our site is going to disappear from the web because the application pool decided to switch itself off.

I know that the Rapid Fail Protection (which causes the switch off after a given number of failures) can be switched off, but I'd rather deal with the underlying issue.

4

1 回答 1

4

原来问题出在 PDF4Net 上,正如应用程序池中的故障转储所揭示的那样。链接如何调试 w3wp clr.dll 错误(由 MikeSmithDev 发布)概述了该过程。

无论如何,出现了一个带有极小页面的pdf,然后会被透明图像盖章。这将创建一个堆栈溢出错误,当多次尝试访问该文件时会导致应用程序池关闭。原来修复只是更新 PDF4Net 的问题。

于 2013-09-06T06:30:28.990 回答