Connection_Abandoned_By_ReqQueue问题 [英] Connection_Abandoned_By_ReqQueue Problems

问题描述

我有这个奇怪的问题。我有3个网站使用完全相同的代码。它们都在同一台专用服务器上，并且都有自己的应用程序池。它是Windows 2008 R2服务器。其中一个站点每隔几个小时就会出现Connection_Abandoned_By_ReqQueue问题。同样，在所有3个站点上都使用相同的代码，但是其中只有一个正在运行。应用程序池具有默认设置。

I have this strange problem. I have 3 sites using the exact same code. All are on the same dedicated server and all have their own app pool. It's Windows 2008 R2 server. One of the sites keeps having the Connection_Abandoned_By_ReqQueue problem every few hours. Again, same code on all 3 sites, but only one is running into that. App pool has default settings.

我读到我应该使用Microsoft的Debug Diagnostics应用程序，并将其安装在我的开发机器上，以便首先使用它，并且没有任何报告显示无法识别（.NET），因此如果服务器上的内容相同，我不确定这将如何帮助我找出问题所在。

I read that I should use Microsoft's Debug Diagnostics app and I installed it on my dev machine to play with it first and none of the reports showed nothing recognizable (.NET) so if it's the same on the server I'm not sure how that will help me track down the problem.

找到这些Connection_Abandoned_By_ReqQueue错误的原因？我已经读过很多东西可能会导致这种情况，但无济于事。

What's the best of finding the cause of these Connection_Abandoned_By_ReqQueue errors? I've read many things can cause this, which doesn't help.

推荐答案

只是向其他读者澄清-错误IIS Http错误日志中记录了 Connection_Abandoned_By_ReqQueue （在％SystemDrive％\Windows\System32\LogFiles\HTTPERR ）

Just to clarify to other readers - the error Connection_Abandoned_By_ReqQueue is logged in the IIS Http error log (under %SystemDrive%\Windows\System32\LogFiles\HTTPERR)

此处的其他潜在原因是堆栈溢出和访问冲突类型异常，由于应用程序的标准错误/异常处理代码和日志记录可能难以跟踪可能会被跳过。

Other potential causes here are Stack Overflows, and Access Violation type exceptions, which can be difficult to track down as the app's standard fault / exception handling code and logging may be skipped.

请确保还检查事件查看器中的应用程序日志。运气好的话，每个故障都将记录一个应用程序错误，并且如果W3WP进程崩溃，则可能会记录Windows错误报告崩溃转储条目。

Be sure to also examine the Application Log in Event Viewer. With some luck, each failure will log an Application Error, and if the W3WP process crashes, a Windows Error Reporting crashdump entry may be logged.

这里是一个堆栈示例溢出（ 0xc00000fd ）

Here's an example of a Stack Overflow (0xc00000fd)

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x52157ba0
Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0x5348961e
Exception code: 0xc00000fd
Fault offset: 0x00001ffb
Faulting process id: 0x3918
Faulting application start time: 0x01d2398c5d2febfc
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: a796f4a2-a581-11e6-80eb-0050569051a9
Faulting package full name: 
Faulting package-relative application ID: 

应用程序日志中的WER故障转储记录将显示您的位置可以找到假人p（这些文件可能在这里提供：C：\ProgramData\Microsoft\Windows\WER\ReportQueue ），然后可以使用诸如WinDbg之类的调试器进行检查

The WER Crash Dump record in the Application Log will show you where you can locate the dump (These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue) which you can then scrutinize with a debugger like WinDbg.

这篇关于Connection_Abandoned_By_ReqQueue问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！