很奇怪的IIS6 asp.net网站的行为 [英] Very weird IIS6 asp.net website behaviour

查看:118
本文介绍了很奇怪的IIS6 asp.net网站的行为的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个奇怪的问题,我的网站。这是托管在专用服务器IIS6 asp.net(.NET 3.5)的网站。

I have a weird issue with my website. This is asp.net(.net 3.5) website hosted on a dedicated server IIS6.

最近我有一个奇怪的现象,该网站挂起,只是没有回复,除非我去到IIS,并重新启动任何应用程序池或整个IIS - 但什么是最奇怪的是,如果我去的远程桌面服务器并尝试访问它在当地它的工作就好了。

Recently I got a strange behavior, the website hangs and just doesn’t reply unless I go to iis and restart either app pool or whole IIS - BUT what is the most strange thing is that in case I go to remote desktop of the server and try to access it locally it DOES work just fine.

我也读到了死锁和悬挂,因为内存泄漏和不封闭的SQL连接,但为什么它仍然没有工作,从地方?

I read couple threads about deadlocking and hanging because of memory leaks and non closed sql connections BUT why it still does work from the local?

在情况下,有什么不对的code - ?为何仍从本地工作

In case there is something wrong with the code – why does it still work from locally?

但如果是在主机端的一些问题(如防火墙问题),那么为什么IISRESET帮助?

In case there is some issues on the hosting side (like firewall issues) then why does iisreset help?

任何想法将AP preciated。谢谢!

Any thoughts would be appreciated. Thank you!

推荐答案

我们刚刚遇到这个问题,我们有一个解决方案。 IIS有两个线程池来处理请求。一个线程池用于外部请求。另一个池用于本地请求。我们的问题是由后台code死锁引起的。一旦发生死锁,所有的外部请求都排队,但不提供服务,因为所有服务线程都在使用中。打开网站从Web服务器使用其他线程池,所以请求的方式。我们absolutley积极的,这是一个网络问题,但WinDbg中证明并非如此。 在这里看到更多的信息: <一href="http://blogs.msdn.com/b/tmarq/archive/2010/04/14/performing-asynchronous-work-or-tasks-in-asp-net-applications.aspx"相对=nofollow>有关IIS和线程的MSDN博客条目

We've just run into this problem, and we have a solution. IIS has two thread pools to handle requests. One thread pool is used for external requests. Another pool is used for local requests. Our problem was caused by a deadlock in backend code. Once the deadlock occurred, all external requests were queued but not serviced because all of the servicing threads were in use. Opening the website from the web server uses the other thread pool, so the requests are serviced. We were absolutley positive it was a network issue, but WinDbg proved otherwise. See here for more information: MSDN blog entry about IIS and threads

<一个href="http://msdn.microsoft.com/en-us/library/system.web.configuration.httpruntimesection.minlocalrequestfreethreads.aspx"相对=nofollow> minLocalRequestFreeThreads

(另外,搜索minFreeThreads看到非本地请求线程池。)

(Also, search for minFreeThreads to see the non-local request thread pools.)

祝你好运!

这篇关于很奇怪的IIS6 asp.net网站的行为的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆