
End of stack trace from previous location where exception was thrown -Īt Program.c_Displa圜lass0_2.b_13>d.MoveNext() in C:\Users\stoub\source\repos\HTTP2Stress\HTTP2Stress\Program.cs:line 173Įrror 4: : An error occurred while sending the request.

> 2ProtocolException: The HTTP/2 request failed with protocol error 'NO_ERROR' (0x0).Īt ()Īt ()Īt 2Connection.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)Īt .SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)Īt .SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)Īt .FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)Īt Program.c_Displa圜lass0_2.b_13>d.MoveNext() in C:\Users\stoub\source\repos\HTTP2Stress\HTTP2Stress\Program.cs:line 177Įrror 3: System.NullReferenceException: Object reference not set to an instance of an object.Īt .GetUriForRedirect(Uri requestUri, HttpResponseMessage response)Īt Program.c_Displa圜lass0_0.b_1>d.MoveNext() in C:\Users\stoub\source\repos\HTTP2Stress\HTTP2Stress\Program.cs:line 100 > System.IO.IOException: The request was aborted. End of inner exception stack trace -Īt (Span`1 buffer)Īt (Memory`1 buffer, CancellationToken cancellationToken)Īt System.IO.Stream.CopyToAsyncInternal(Stream destination, Int32 bufferSize, CancellationToken cancellationToken)Īt .GetStringAsyncCore(Task`1 getTask)Īt Program.c_Displa圜lass0_2.b_17>d.MoveNext() in C:\Users\stoub\source\repos\HTTP2Stress\HTTP2Stress\Program.cs:line 173```Įrror 2: : An error occurred while sending the request. > 2ProtocolException: The HTTP/2 request failed with protocol error 'FRAME_SIZE_ERROR' (0圆).Īt 2Connection.ReadFrameAsync(Boolean initialFrame)Īt 2Connection.ProcessIncomingFramesAsync() ConcurrentRequests, AppxContentLength) as well as by commenting and uncommenting out which client operations were available to be performed in a given run.Įrror 1: System.IO.IOException: The request was aborted.

These were encountered by varying some of the constants (e.g. The below is based on the most recent daily build as of now. Some are obviously issues with SocketsHttpHandler, but some could be on either end of the connection (and a few are likely to be Kestrel). In doing so, I encountered a variety of failures in a very short period of time (seconds).

I wrote a simple stress program to exercise many concurrent requests from HttpClient against Kestrel, specifically for HTTP/2. We can decide if/when to break out individual issues.) (I'm opening one issue right now because I don't have individual repros for each of the following issues, and it’s possible one or more are related.
