« Previous Next »

Thread: Uploads fail / timeout

Last post 09-16-2009 9:19 AM by Mark S. Rasmussen. 3 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (4 items)

Sort Posts:

  • 09-15-2009, 4:56 AM

    Uploads fail / timeout

    We allow our users to upload files to our system through a Flash uploading application. If I request the sites on the servers directly, everything works as it should. If I request the site through the ARR load balancer the uploads timeout after about 2 minutes. Downloads work as expected. This is my configuration:

         <webFarms>
            <webFarm name="iPaper" enabled="true">
                <server address="MGM" enabled="true" />
                <server address="MANDALAY" enabled="true" />
                <applicationRequestRouting>
                    <protocol timeout="01:00:00" includePortInXForwardedFor="false">
                        <cache enabled="false" />
                    </protocol>
                    <affinity useCookie="true" cookieName="IPARRAffinity" />
                </applicationRequestRouting>
            </webFarm>
            <applicationRequestRouting>
                <hostAffinityProviderList>
                    <add name="Microsoft.Web.Arr.HostNameRoundRobin" />
                    <add name="Microsoft.Web.Arr.HostNameMemory" />
                </hostAffinityProviderList>
            </applicationRequestRouting>
        </webFarms>

    No rewriting is being done and caching is disabled. I imagine the <protocol timeout> attribute defines the timeout for downloads. Is there anywhere I can set the timeout setting for incoming requests?

    Thanks!
    Mark S. Rasmussen

  • 09-15-2009, 9:52 AM In reply to

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

    Re: Uploads fail / timeout

    Can you collect failed request trace for the request that times out and send me the logs at anil (dot) ruia (at) microsoft (dot) com - make sure that the RequestRouting area is selected among the areas under WWW Server for your trace rule.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 09-16-2009, 4:23 AM In reply to

    Re: Uploads fail / timeout

    Hi Anil,

    I've tried setting up FREB to catch the request traces, but I'm unable to do so. Apparently the request is never received / handled properly.

    By making a console app perform the request manually I'm able to see the actual error: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.

    This error only occurs when going through the ARR machine, if I circumvent it by switching IP's in the hosts file, everything works fine.

    On the ARR machine I've set the maxRequestLength & executionTimeout values as I thought those might have a say, but they don't seem to affect the issue.
    <httpRuntime maxRequestLength="2097151" executionTimeout="3600"/>

    I'm suspecting this is probably a configuration setting in the IIS that may not be related to ARR, though it manifests itself in the missing ARR reply.

    Let me know if I can give any further info that may help. Thanks.
  • 09-16-2009, 9:19 AM In reply to

    Re: Uploads fail / timeout

    I've solved the issue.

    By enabling normal IIS logging on both the content servers as well as the ARR machine I was able to see that the request never reached the content servers. Looking through the ARR machine I noted that a 404 status was returned - a 404.13 specifically.

    Looking through the documentation it quickly became apparent that request filtering was the issue. The request was quenched by requets filtering before reaching the URL Rewriting / ARR module and was thus completely unrelated to ARR.

    Upping the request filtering request length solved the problem.
Page 1 of 1 (4 items)
Microsoft Communities