ASP.NET Core (-4077,–4047,–4089, 4095)


If you get any of these errors, take a memory dump of your process, like I discuss below and look at the stacks.

I found this pattern in a Failed Request Trace log.

freb001

Once you get the memory dump, open it in WinDbg and Dump All Exceptions and you might see the following:

Type: Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvException
Message: Error -4077 ECONNRESET connection reset by peer

Type: System.Threading.Tasks.TaskCanceledException
Message: The request was aborted

Dump out all the threads and look for a stack similar to this:

libuv!uv_poll_ex
libuv!uv_run
Microsoft_ServiceBus!DomainBoundILStubClass.IL_STUB_PInvoke(Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvLoopHandle, Int32)
Microsoft_AspNetCore_Server_Kestrel!Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.Libuv.run(Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvLoopHandle, Int32)
Microsoft_AspNetCore_Server_Kestrel!Microsoft.AspNetCore.Server.Kestrel.Internal.KestrelThread.ThreadStart(System.Object)

Also, dump out the version of the Microsoft_AspNetCore_Server_Kestrel module:

lmvm Microsoft_AspNetCore_Server_Kestrel
.....
.....
Image name: Microsoft.AspNetCore.Server.Kestrel.dll
File version:     1.0.1.20831
Product version:  1.0.1.0
....

If you find similar symptoms then the problem is that you need to update to at least 1.0.3, but recommend upgrading to the newest version, as of writing this article here, which is 1.1.

You can read more about this on GitHub:

Comments (0)

Skip to main content