什么时候加载IIS7太多了？

问题描述

在我们的客户，候选人与我们的软件测试。如果他们的测试完成，一些计算在服务器上完成。现在，有时候，200名考生可以同时结束考试，所以200个考试是同时进行的。计算似乎都很好，但一些调用到IIS7服务器得到一个http错误...

在Flex中，这是错误：

$ p $ code =NetConnection.Call.Failed
description =HTTP：Status 200
details =http： //servername/weborb.aspx
level =error


不是状态200好吗？那么这里有什么问题？它甚至是IIS7的问题？在200名候选人中，20人得到了这个信息。当重新开始测试时，一切正常。

我发现，但我想知道这是否与我的问题有关（下周我们的客户将做一些stresstests和我我们已经要求他们测试这个帖子中的解决方案是否有效。）

一些问题：

$ ul b $ b

当负载过多时，IIS7是否可以阻止某些http调用？

如何知道IIS7因负载过重而阻止了这些调用？ >

有没有可能配置这些东西？

从技术上讲，将来我想排队计算，但现在，没有时间也没有预算。

应用程序：Flex，WebORB，ASP.NET，IIS7和SQLSERVER2008。服务器是Windows Server 2008的。

解决方案

这个问题对我来说似乎很熟悉。我们有一些flex小部件连接到一个服务器端，有时它也返回Netconnection.Call.Failed。对我们来说，似乎IIS（后面的MSSql）不能及时处理所有的请求，因此其中有一些是超时的。
尝试检查每个请求/所有请求需要多少时间，然后检查您的超时设置。

At a customer of ours, candidates take tests with our software. If their test is finished, some calculations are done on the server. Now, sometimes, 200 candidates can end their test at the same time, so 200 calculations are done concurrent. The calculations all seem to go fine, but some calls to the IIS7 server get back a http error...

In Flex, this is the error:

code = "NetConnection.Call.Failed"
description = "HTTP: Status 200"
details = "http://servername/weborb.aspx"
level = "error"

Isn't Status 200 OK? So what's wrong here? Is it even a IIS7 problem? Of the 200 candidates 20 got this message. When restarting their test, everything worked well.

I have found this on the subject, but I wonder if this has anything to do with my problem (next week our customer will do some stresstests and I'll already asked them to test test if solution in this post works).

Some questions:

• Can it be that IIS7 blocks certain http calls when load is to much?
• How can you know that IIS7 blocked those calls because of too much load?
• Is it possible to configure these things?

Technically, in the future I would like to queue the calculations, but for now, there isn't time nor budget for that.

Application: Flex, WebORB, ASP.NET, IIS7 en SQLSERVER2008. Server is Windows Server 2008.

解决方案

This problem seems very familiar to me. We have a bunch of flex widgets which are connected to one server-side and sometimes it also returns "Netconnection.Call.Failed". For us, it seems that the IIS(and MSSql behind) cannot process all the requests in time, hence some of them are timed out.Try to check how much time each request/all requests take, then check your timeout setting.

这篇关于什么时候加载IIS7太多了？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！