调试挂网站
我们为客户构建和托管的 ASP.NET 网站遇到了问题。大约一周前，该网站只是无法响应请求，没有返回任何错误。我们没有部署任何代码，但客户端确实会不时上传未编译的页面。
重新启动网站运行的应用程序池可以解决问题，但 1-8 小时后，同样的情况将会再次发生。
奇怪的是，iis 日志显示，虽然站点似乎没有响应，但页面似乎正常提供服务，几乎就像请求被困在队列或其他东西中一样。
服务器的事件日志也没有显示任何异常情况。该站点在 2 台服务器上运行，这些服务器使用 NLB 进行负载平衡。将负载切换到一台服务器然后另一台服务器显示相同的结果，表明问题不是特定于环境的，而是应用程序本身的问题。
我们运行了 DebugDiag，也没有明显的结果。我们现在不知道该去哪里查清真相。谁能建议一些我们可以用来消除任何问题或发现问题根源的调试技术？
We have a problem with an asp.net website we part build and host for a client. About a week ago the website would just failed to respond to requests, no error was returned. No code was deployed by us but the client does upload non compiled pages from time to time.
Restarting the app pool the site runs on fixes the problem but in 1-8 hours the same will happen again.
The strange thing is that the iis log shows that, while the site appears to not be responding, pages appear to be served as normal, almost as if requests are stuck in a queue or something.
The event log of the server shows nothing out of the ordinary either. The site is run on 2 servers which are load balanced using NLB. Switching the load onto one server then another shows the same results indicating that the issue is not environment specific but an issue with the application itself.
We have run DebugDiag with no obvious results too. We are not sure where to go with getting to the bottom of this now. Can anyone suggest some debugging techniques we could use to eliminate anything or discover the source of the issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
CPU 使用情况如何？它是否已达到极限（如果您设置了限制，则可能是应用程序池的极限）？
是从数据库中读取吗？是否死锁或卡住，导致页面无法加载？
Whats CPU usage like? is it maxed out (possibly maxed for the app pool if youve set a limit)?
Is it reading from a database? Is it deadlocked or otherwise stuck, preventing the pages from loading?
只是一个“白页”结果 - 所以客户端没有错误，但也没有响应流？
如果是这样，我们的旧应用程序就会得到相同的结果。从经典 ASP 到 .NET 1.0、1.1 以及最终的 2.0。
我们忘记终止原始构建中留下的一些“静态”变量，它们每隔x小时变得非常“静态”，导致应用程序变成“白色”。
Just a "white page" result - so no error to the client, but no response stream either?
If so, we've had the same results with a legacy app of ours. From classic ASP to .NET 1.0, 1.1 and eventually 2.0.
We forgot to terminate some "static" variables left from the original built and they became very "static" every x hours causing the app to go "white".