We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

View Complete Thread
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Dec 15, 2008 10:35 AM|Alexey.UA|LINK

    Hi Thomas,

    You have stated that "with the fix you will not see any exceptions when the client is disconnected while ASP.NET reads the entity body."

    And what about flushing the response? Would it be throwing an exception in both Integrated and Classic modes in the same case?

    Following exceptions can be thrown when client is disconnected while flushing, but Classic mode one seems to be somehow intermittent:

    An error occurred while communicating with the remote host. The error code is 0x80070057.:   
    at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async)
    at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
    at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
    at System.Web.HttpResponse.Flush(Boolean finalFlush)
    at System.Web.HttpResponse.Flush()
    at ASP.default_aspx.Page_Load(Object sender, EventArgs e)

    The remote host closed the connection. The error code is 0x80070057.:
    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 ASP.default_aspx.Page_Load(Object sender, EventArgs e)