Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows 2008 / IIS 7.5 server that I want to act as a proxy for another service call.

The problem I am having is that the service I am calling often takes a while to respond, so I need the proxy to:

  • not timeout
  • handle as many incoming requests as it can, because it does not work other than pass the request off to the service, and wait for a response.

Can anyone offer any advice on how I can configure such a setup?

share|improve this question

migrated from Jul 2 '11 at 0:56

This question came from our site for professional and enthusiast programmers.

For the first part you could refer to How to increase request timeout in IIS7.0? to configure connection and execution timeout settings for your application. It's for iis 7.0 but probably will work for 7.5 too.

For the second part of your question, you have to configure application pool settings. You can find information about how to do that in this document.

share|improve this answer

You usually set capacity (i.e. number of threads) limits and timeout limits in your application framework (ASP, ASP.Net, etc).

If there are threading or memory scalability limiting issues, you might want to consider setting numProcesses > 1 , which creates a Web Garden; if your app requires state (or rather, is not stateless), a Web Garden isn't an appropriate choice unless you're using some form of out-of-process state.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.