blocks|key|3641604|text|关键是“没有任何痕迹”。您需要将自己的跟踪记录放入日志中，以创建一些对话。然后你就能发现聊天在哪里停止了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3641605|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The key is "without any trace". You need to put your own trace logging in to create some chatter. Then you'll be able to spot where the chatter stops.

blocks|key|5755770|text|asp.net+process的崩溃转储应该会给你tons+of+info..If你想要快速获得一些关于为什么进程被回收的信息，try+this+tip+from+Scott+Gu..asp.net+2.0的Health+monitoring特性也值得一看。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5755771|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/tess/archive/tags/ASP.NET/default.aspx|1|http://blogs.msdn.com/tess/pages/net-debugging-demos-information-and-setup-instructions.aspx|2|http://weblogs.asp.net/scottgu/archive/2005/12/14/433194.aspx|3|http://odetocode.com/Blogs/scott/archive/2005/11/01/2402.aspx^0|0|F|0|P|C|1|1S|Q|2|2W|H|3|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]|$A|Y|B|Z|1|10]|$A|11|B|12|1|13]]|C|$]]|$1|D|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]|P|$5|G|H|I|C|$J|Q]]]]

Crash dump of <a href="http://blogs.msdn.com/tess/archive/tags/ASP.NET/default.aspx" rel="nofollow noreferrer">asp.net process</a> should give you <a href="http://blogs.msdn.com/tess/pages/net-debugging-demos-information-and-setup-instructions.aspx" rel="nofollow noreferrer">tons of info</a>..If you want to quickly get some info on why the process got recycled, <a href="http://weblogs.asp.net/scottgu/archive/2005/12/14/433194.aspx" rel="nofollow noreferrer">try this tip from Scott Gu</a>..
<a href="http://odetocode.com/Blogs/scott/archive/2005/11/01/2402.aspx" rel="nofollow noreferrer">Health monitoring</a> feature of asp.net 2.0 is also worth looking at..

blocks|key|5755807|text|ASP.NET跟踪...http://www.beansoftware.com/ASP.NET-Tutorials/Tracing-ASP.NET.aspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5755808|entityMap|0|LINK|mutability|MUTABLE|url|http://www.beansoftware.com/ASP.NET-Tutorials/Tracing-ASP.NET.aspx^0|C|1U|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

ASP.NET Tracing...
<a href="http://www.beansoftware.com/ASP.NET-Tutorials/Tracing-ASP.NET.aspx" rel="nofollow noreferrer">http://www.beansoftware.com/ASP.NET-Tutorials/Tracing-ASP.NET.aspx</a>

blocks|key|532134|text|下载Windows环境下的调试工具：http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|532135|调试工具有一个脚本(ADPLUS)，允许您在进程崩溃时创建转储：http://support.microsoft.com/kb/286350|532136|命令应该类似于(如果您使用的是IIS6)：|532137|cscript+adplus.vbs+-crash+-pn+w3wp.exe|code-block|syntax|javascript|532138|此命令会将调试器附加到辅助进程。当崩溃发生时，它将生成一个转储(一个*.DMP文件)。|532139|您可以在WinDBG中打开它(也包含在Windows的调试工具中)。文件>打开崩溃转储...|532140|默认情况下，WinDBG将(在命令行旁边)显示进程崩溃时的线程。|532141|在WinDBG中，您需要做的第一件事是加载.NET框架扩展：|532142|.loadby+sos+mscorwks|532143|然后，您将显示托管调用堆栈：|532144|!clrstack|532145|如果线程没有运行托管代码，则需要检查本机堆栈：|532146|kpn+200|532147|这应该会给你一些想法。要继续进行故障诊断，我建议您阅读以下文章：|532148|http://msdn.microsoft.com/en-us/library/ms954594.aspx|532149|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx|1|http://support.microsoft.com/kb/286350|2^0|I|1P|0|0|W|12|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|1H|2|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@$A|1K|B|1L|1|1M]]|C|$]]|$1|D|3|E|5|6|7|1N|8|@]|9|@$A|1O|B|1P|1|1Q]]|C|$]]|$1|F|3|G|5|6|7|1R|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1S|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1T|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1U|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1V|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1W|8|@]|9|@]|C|$]]|$1|U|3|V|5|J|7|1X|8|@]|9|@]|C|$K|L]]|$1|W|3|X|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|J|7|1Z|8|@]|9|@]|C|$K|L]]|$1|10|3|11|5|6|7|20|8|@]|9|@]|C|$]]|$1|12|3|13|5|J|7|21|8|@]|9|@]|C|$K|L]]|$1|14|3|15|5|6|7|22|8|@]|9|@]|C|$]]|$1|16|3|17|5|6|7|23|8|@]|9|@$A|24|B|25|1|26]]|C|$]]|$1|18|3|-4|5|6|7|27|8|@]|9|@]|C|$]]]|19|$1A|$5|1B|1C|1D|C|$1E|1F]]|1G|$5|1B|1C|1D|C|$1E|1H]]|1I|$5|1B|1C|1D|C|$1E|17]]]]

Download Debugging tools for Windows:
<a href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx" rel="nofollow noreferrer">http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx</a>

Debugging Tools for Windows has has a script (ADPLUS) that allows you to create dumps when a process CRASHES:
<a href="http://support.microsoft.com/kb/286350" rel="nofollow noreferrer">http://support.microsoft.com/kb/286350</a>

The command should be something like (if you are using IIS6):

<pre><code>cscript adplus.vbs -crash -pn w3wp.exe
</code></pre>

This command will attach the debugger to the worker process. When the crash occurs it will generate a dump (a *.DMP file).

You can open it in WinDBG (also included in the Debugging Tools for Windows). File > Open Crash dump...

By default, WinDBG will show you (next to the command line) the thread were the process crashed.

The first thing you need to do in WinDBG is to load the .NET Framework extensions:

<pre><code>.loadby sos mscorwks
</code></pre>

then, you will display the managed callstack:

<pre><code>!clrstack
</code></pre>

if the thread was not running managed code, then you'll need to check the native stack:

<pre><code>kpn 200
</code></pre>

This should give you some ideas. To continue troubleshooting I recommend you read the following article:

<a href="http://msdn.microsoft.com/en-us/library/ms954594.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms954594.aspx</a>

blocks|key|3641706|text|试试这个https://www.leansentry.com/+--轻量级的应用程序监控，它可以自动诊断服务器问题！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3641707|entityMap|0|LINK|mutability|MUTABLE|url|https://www.leansentry.com/^0|4|R|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Try this <a href="https://www.leansentry.com/" rel="nofollow">https://www.leansentry.com/</a> - Lightweight application monitoring that automatically diagnoses server problems!

I am working on an ASP.NET web application, it seems to be working properly when I try to debug it in Visual Studio. However when I emulate heavy load, IIS crashes without any trace -- log entry in the system journal is very generic, "The World Wide Web Publishing service terminated unexpectedly. It has done this 4 time(s)."
How is it possible to get more information from IIS to troubleshoot this problem?

IIS crashes when serving an ASP.NET application under heavy load. How to troubleshoot it?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在开发一个ASP.NET web应用程序，当我尝试在Visual Studio中调试它时，它似乎工作正常。但是，当我模拟重载时，IIS崩溃而没有任何跟踪--系统日志中的日志条目非常常见，“World Wide Web Publishing服务意外终止。它已经这样做了4次。”如何从IIS获取更多信息来解决此问题？

问在负载过重的情况下为ASP.NET应用程序提供服务时，IIS崩溃。如何进行故障排除？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在负载过重的情况下为ASP.NET应用程序提供服务时，IIS崩溃。如何进行故障排除？EN