多次调用同一个Web服务阻止？ [英] Multiple Calls to the same Web Service Blocking?

问题描述

我们有一个页面，使一个3'rd第三方Web服务的请求。在重负载下的这个响应时间延长显著，但是3'rd方报告回有时间处理保持不变。有计时显示，从时间他们收到他们发回的时候要求总是围绕1.5-2.0秒。现在，我们正在经历的在20秒的等待时间。我的ASP.NET的理解是，每个请求将在一个IIS线程池中的线程中运行，使请求3'rd方的服务回报和流程。所以，我真的不明白什么可以在我们这边会阻止。有什么我失踪？是否有门槛限制超出IIS正在阻止？

We have a page that makes a request to a 3'rd party web service. When under heavy load this response time extends significantly, however the 3'rd party reports back that there times for processing remains constant. There timings show that from the time they receive a request to the time they send it back is always around 1.5-2.0 seconds. Now we are experiencing wait times of over 20 seconds. My understanding of ASP.NET is that each request will run on a IIS thread pool thread and make the request to the 3'rd party service return and process. So I don't really understand what could be blocking on our end. Is there something I am missing?? Is there a threshold limit beyond IIS that is blocking?

如果我失去了一些东西，涵盖这个问题也将是一个非常值得欢迎的除了任何回答实体书的建议。

If I am missing something a physical book recommendation that covers this subject would also be a very welcome addition to any answer.

推荐答案

.NET限制实施2个并发Web请求到一台主机的限制。所以你的情况这并不是说需要更多的时间来执行Web服务，但您的应用程序延迟请求留此约束内。

.NET limits enforces a limit of 2 concurrent web requests to a single host as suggested by the HTTP specification. So in your case it's not the web service that needs more time to execute, but your application delaying the requests to stay inside this constraint.

您可以通过添加此键，您的配置文件，提高对Web服务的限制：

You can raise the limit for the web service by adding this key to your config file:

  <system.net>
    <connectionManagement>
      <!-- specific servers... -->
      <add address="http://example.org" maxconnection="20" />

      <!-- ...or any server -->
      <add address="*" maxconnection="8" />
    </connectionManagement>
  </system.net>

这篇关于多次调用同一个Web服务阻止？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！