1

Closed

System.Web.HttpException: The remote host closed the connection. The error code is 0x80070040.

description

I get the following error in my ELMAH error logs quite often for the combining url? Any help would be appreciated.

System.Web.HttpException: The remote host closed the connection. The error code is 0x80070040.

System.Web.HttpException (0x80070040): The remote host closed the connection. The error code is 0x80070040.
at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
at System.Web.HttpResponse.Flush(Boolean finalFlush)
at System.Web.HttpResponse.Flush()
at Combres.RequestProcessor.SendOutputToClient(Byte[] bytes, Boolean insertCacheHeaders, String etag) in D:_Data\Personal\Projects\Combres\Combres\Engine\RequestProcessor.cs:line 161
at Combres.RequestProcessor.WriteFromServerCache() in D:_Data\Personal\Projects\Combres\Combres\Engine\RequestProcessor.cs:line 226
at Combres.DefaultProcessingWorkflow.Execute() in D:_Data\Personal\Projects\Combres\Combres\Engine\DefaultProcessingWorkflow.cs:line 53
at Combres.RequestProcessor.Execute() in D:_Data\Personal\Projects\Combres\Combres\Engine\RequestProcessor.cs:line 107
at Combres.CombresHandler.ProcessRequest(HttpContext context) in D:_Data\Personal\Projects\Combres\Combres\API\CombresHandler.cs:line 49
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Closed May 28, 2010 at 10:04 AM by
Fixed

comments

buunguyen wrote May 3, 2010 at 3:10 PM

I've never seen this. I've googled for that error, e.g. http://forums.iis.net/t/1165399.aspx, and it seems to me like this happens because the user/browser disconnects/timeouts in the middle of Response.Flush() on the server.

You might want to check if your resource set is too big - big sets may take more time to be combined, minified, gzipped & downloaded and the impatient users may explicitly stop the page or the browsers may just timeout the connection.

I've also added a line 'if (response.IsClientConnected)' before 'response.Flush()' in the latest source code commit. Hopefully you won't see the error again (or it will appear much less frequently).

abo123y wrote Aug 15, 2016 at 5:43 AM

hi I've got this issue too. How did you fix it?