asp.net - Long running HttpWebRequests -


I have an asp.net web application running on IIS6 server. This application is making potential long-term calls to an XML service on a remote machine. Long-term solution calls for making asynchronous calls (sometimes up to 4 minutes) for some service calls on the remote machine, but as a short-term solution, we call the timeout and the overall httpRequest time Want to increase

My fear is that with the long running, filling the call request queue and preventing the "normal" page request will stop. How can the server, IIS, and application settings be tuned to solve the problem?

Currently there are about 200 page requests / minutes and result in 270 service requests / minutes.

  • Current execution timeout 360 (6 minutes)
  • The time for the current service call is 2 minutes

This article on Microsoft's Knowledgebase has some of the information you may have:

*


I have done some research about some specific items in the article which I have done above. The information below applies to IIS6, where comments for IIS7 are applicable.

Increase processor thread thread 25 to less than 100

The default value for Threadpool size is 100 because true

> maximumconnection
  • There is a value that is still 25 Changed - it can only be set in the IIS metabase ( adsutil device) in [IIS 7 is equivalent value of IIS6]

    so I machine.config I'm not choosing to change the settings because they are okay and other parameters And who will be affected by the closing autoconfig , but the change in 100 from 25 through IIS Metabase (The only way to change this value).

    For example

      cscript% SYSTEMDRIVE% \ Inetpub \ AdminScripts \ & lt; Nowiki & gt; Adsutil.vb & lt; / Nowiki & gt; SET W3SVC / AspRequestQueueMax 100  

    Maximum connection per server

    Autoconfig sets this value in the 12 * number of the CPU, in this way From how many connections you are making to each address, how many connections can they make.

  • Nbsp; & Nbsp; & Nbsp; ASP.NET Application / Request Queue
  • This will show us that if the items of work are queued due to lack of workers.

    Check IIS Manager
  • Check which application pool is used by your site in IIS Manager
  • Select application pool Applications Pool is used in the list, then right-click - & gt; See the properties and how the account identity is being used.
  • It should be network service by default.

  • Comments

    Popular posts from this blog

    sql - dynamically varied number of conditions in the 'where' statement using LINQ -

    asp.net mvc - Dynamically Generated Ajax.BeginForm -

    Debug on symbian -