« Previous Next »

Thread: Long running ARR requests abort and are not logged

Last post 09-02-2009 12:05 PM by anilr. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

  • 09-02-2009, 10:25 AM

    Long running ARR requests abort and are not logged

    Hi -

    We're trying to get ARR beta 2 up and running. We have 2 ARR proxy servers routing all requests to 2 IIS servers. If one of the IIS servers takes a long time to serve a page, the ARR server dumps the request somehow and returns this response: "The specified CGI application encountered an error and the server terminated the process." (there's no HTML formatting around it). If I visit the page directly (rather than through ARR), the page serves correctly. I've got a page doing Thread.Sleep to test this behaviour and it's 100% reproducible - it seems to die after 30 seconds.

    The server farm's Proxy element has a "Time-out" section that's set to 30 seconds - but changing this doesn't stop the error message.

    Nothing gets left in the event log on the ARR boxes, and searching for this message on the net yields no results - so I'm a bit stuck how to troubleshoot!

    Any ideas on what might be going wrong, and what I can do to stop it happening? At the very least, how can I return a friendly error page rather than this awful one liner!

    Thanks!
  • 09-02-2009, 12:05 PM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,343

    Re: Long running ARR requests abort and are not logged

    The error is caused by that timeout - you must not be changing the timeout in the correct place, note that there are timeouts configured at "server proxy" or at "server farm" level.  Also, you can use IIS custom errors to customize 502.3 errors.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
Page 1 of 1 (2 items)
Microsoft Communities