HTTP/3: Error when multiple connections to a server

[JamesNK]

Description

I've noticed the gRPC benchmark has failed requests when there are multiple connections.

Reproduction Steps

1. git clone https://github.com/jamesnk/grpc-dotnet
2. git checkout jamesnk/net7
3. dotnet run -c Release --project .\perf\benchmarkapps\GrpcAspNetCoreServer\ -- --LogLevel Trace --protocol h3
4. dotnet run -c Release --project .\perf\benchmarkapps\GrpcClient\ -- -u https://localhost:5000 -c 2 --streams 1 -s unary -p h3 --grpcClientType grpcnetclient --LogLevel Trace --callCount 10

Expected behavior

Requests all succeed.

Actual behavior

One or two requests fail. Also, the client app takes a long time (20 seconds?) to close. I think a request on one of the connections is hung.

Client and server logs are attached.

• server.log
• client.log

Regression?

I think so.

Known Workarounds

No response

Configuration

No response

Other information

No response

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

I've noticed the gRPC benchmark has failed requests when there are multiple connections.

Reproduction Steps

1. git clone https://github.com/jamesnk/grpc-dotnet
2. git checkout jamesnk/net7
3. dotnet run -c Release --project .\perf\benchmarkapps\GrpcAspNetCoreServer\ -- --LogLevel Trace --protocol h3
4. dotnet run -c Release --project .\perf\benchmarkapps\GrpcClient\ -- -u https://localhost:5000 -c 2 --streams 1 -s unary -p h3 --grpcClientType grpcnetclient --LogLevel Trace --callCount 10

Expected behavior

Requests all succeed.

Actual behavior

One or two requests fail. Also, the client app takes a long time (20 seconds?) to close. I think a request on one of the connections is hung.

Client and server logs are attached.

• server.log
• client.log

Regression?

I think so.

Known Workarounds

No response

Configuration

No response

Other information

No response

Author:	JamesNK
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[JamesNK]

I tested this more and found the problem is related to #72511.

It turns out the answer to my first question here is no, the callback doesn't run when AcceptConnectionAsync is called. It runs in the background as connections are received.