Quarantine ResponseBody_WriteContentLength_PassedThrough

[wtgodbe]

Failing Test(s)

• Microsoft.AspNetCore.Server.HttpSys.ResponseBodyTests.ResponseBody_WriteContentLength_PassedThrough

Error Message

System.Net.Http.HttpRequestException : An error occurred while sending the request.
---- System.IO.IOException : Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
-------- System.Net.Sockets.SocketException : An existing connection was forcibly closed by the remote host.

Stacktrace

Details

   at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Microsoft.AspNetCore.Server.HttpSys.ResponseBodyTests.SendRequestAsync(String uri) in /_/src/Servers/HttpSys/test/FunctionalTests/ResponseBodyTests.cs:line 441
   at Microsoft.AspNetCore.Server.HttpSys.ResponseBodyTests.ResponseBody_WriteContentLength_PassedThrough() in /_/src/Servers/HttpSys/test/FunctionalTests/ResponseBodyTests.cs:line 222
--- End of stack trace from previous location ---
----- Inner Stack Trace -----
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
   at System.Net.Http.HttpConnection.InitialFillAsync(Boolean async)
   at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
----- Inner Stack Trace -----

Logs

Details

2025-09-03T21:35:52.5571904Z [xUnit.net 00:00:11.68]         | [0.001s] TestLifetime Information: Starting test ResponseBody_WriteContentLength_PassedThrough at 2025-09-03T21:35:52
2025-09-03T21:35:52.5575129Z [xUnit.net 00:00:11.68]         | [0.002s] Microsoft.AspNetCore.Server.HttpSys.HttpSysListener Debug: Listening on prefix: http://localhost:5110/
2025-09-03T21:35:52.5577957Z [xUnit.net 00:00:11.68]         | [0.004s] Microsoft.AspNetCore.Server.HttpSys.HttpSysListener Debug: Flush; Ignored write exception: 87
2025-09-03T21:35:52.5581097Z [xUnit.net 00:00:11.68]         | [0.005s] Microsoft.AspNetCore.Server.HttpSys.HttpSysListener Information: Stop listening on prefix: http://localhost:5110/
2025-09-03T21:35:52.5582969Z [xUnit.net 00:00:11.68]         | [0.005s] Microsoft.AspNetCore.Server.HttpSys.MessagePump Debug: Failed to accept a request, the server is stopping.
2025-09-03T21:35:52.5584619Z [xUnit.net 00:00:11.68]         | Microsoft.AspNetCore.Server.HttpSys.HttpSysException (995): The I/O operation has been aborted because of either a thread exit or an application request.
2025-09-03T21:35:52.5586373Z [xUnit.net 00:00:11.68]         |    at Microsoft.AspNetCore.Server.HttpSys.AsyncAcceptContext.IOCompleted(UInt32 errorCode, UInt32 numBytes, Boolean managed) in /_/src/Servers/HttpSys/src/AsyncAcceptContext.cs:line 69
2025-09-03T21:35:52.5588131Z [xUnit.net 00:00:11.68]         | --- End of stack trace from previous location ---
2025-09-03T21:35:52.5589812Z [xUnit.net 00:00:11.68]         |    at Microsoft.AspNetCore.Server.HttpSys.AsyncAcceptContext.GetResult(Int16 token) in /_/src/Servers/HttpSys/src/AsyncAcceptContext.cs:line 275
2025-09-03T21:35:52.5591636Z [xUnit.net 00:00:11.68]         |    at Microsoft.AspNetCore.Server.HttpSys.MessagePump.AcceptLoop.ExecuteAsync() in /_/src/Servers/HttpSys/src/MessagePump.cs:line 256
2025-09-03T21:35:52.5593501Z [xUnit.net 00:00:11.68]         | [0.005s] Microsoft.AspNetCore.Server.HttpSys.MessagePump Debug: Failed to accept a request, the server is stopping.
2025-09-03T21:35:52.5595230Z [xUnit.net 00:00:11.68]         | Microsoft.AspNetCore.Server.HttpSys.HttpSysException (995): The I/O operation has been aborted because of either a thread exit or an application request.
2025-09-03T21:35:52.5606691Z [xUnit.net 00:00:11.68]         |    at Microsoft.AspNetCore.Server.HttpSys.AsyncAcceptContext.IOCompleted(UInt32 errorCode, UInt32 numBytes, Boolean managed) in /_/src/Servers/HttpSys/src/AsyncAcceptContext.cs:line 69
2025-09-03T21:35:52.5621081Z [xUnit.net 00:00:11.68]         | --- End of stack trace from previous location ---
2025-09-03T21:35:52.5623266Z [xUnit.net 00:00:11.68]         |    at Microsoft.AspNetCore.Server.HttpSys.AsyncAcceptContext.GetResult(Int16 token) in /_/src/Servers/HttpSys/src/AsyncAcceptContext.cs:line 275
2025-09-03T21:35:52.5625353Z [xUnit.net 00:00:11.68]         |    at Microsoft.AspNetCore.Server.HttpSys.MessagePump.AcceptLoop.ExecuteAsync() in /_/src/Servers/HttpSys/src/MessagePump.cs:line 256

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1136068&view=results

Related:
#4347
#51788
dotnet/runtime#90338

[github-actions]

Investigation

This test has been failing intermittently in CI. The failure pattern shows:

1. The HttpSys server starts listening and processes the request
2. The server encounters a "Flush; Ignored write exception: 87" (error code 87 = ERROR_INVALID_PARAMETER, which can be transient in HTTP.sys)
3. The server stops listening very quickly (within ~7ms of starting)
4. The client HttpRequestException with SocketException (10054): An existing connection was forcibly closed by the remote host occurs

The root cause appears to be a race condition during HttpSys server shutdown or request processing. The test uses synchronous I/O (AllowSynchronousIO = true) and mixes BeginWrite/EndWrite with async WriteAsync. The flush error (code 87) suggests HttpSys is rejecting the write operation, possibly because the response is being flushed/aborted before all writes complete.

This is likely the same underlying race condition tracked in #4347 and #51788, related to HttpSys write completion racing with connection teardown.

A quarantine PR has been opened to add [QuarantinedTest] to this test: #aw_rbpr1

Generated by Daily Test Quarantine Management · ◷