MsQuic client is not getting notified when the server exits in a particular scenario.

[ashish284]

In my use case, MsQuic client is calling ConnectionOpen/ConnectionStart in a loop till the server is listening and connection is accepted.

Unfortunately because of an error in server application, it starts (1), then exits (2) and then restart (3) again immediately (will continue to run properly after this point).

When the server application start for the first time (1), the connection is getting established with MsQuic client but when it exits (2) client is not getting notified about this disconnection and client keeps on sending data to server. Upon restart (3) , the data is not getting passed to the server application.

From the etl logs on server side, I could see the following (3):
[4]5460.8C08::2025/03/19-12:12:04.772294800 [Microsoft-Quic][pack][7696581394579] Received
[4]5460.8C08::2025/03/19-12:12:04.772296700 [Microsoft-Quic][bind][0x2337E42D840] DROP packet Dst=192.168.50.207:8888 Src=192.168.50.175:45021 Reason=Already in stateless oper table.
[4]5460.8C08::2025/03/19-12:12:04.782747600 [Microsoft-Quic][data][0x2337E2BCE80] Recv 741 bytes (segment=741) Src=192.168.50.207:8888 Dst=192.168.50.175:45021
[4]5460.8C08::2025/03/19-12:12:04.782748500 [Microsoft-Quic][pack][7696581394580] Received
[4]5460.8C08::2025/03/19-12:12:04.782756000 [Microsoft-Quic][wrkr][0x2337E2ADF50] IsActive = 1, Arg = 4006319521
[4]5460.8C08::2025/03/19-12:12:04.782756600 [Microsoft-Quic][bind][0x2337E42D840] Execute: 10(RETRY)
[4]5460.8C08::2025/03/19-12:12:04.782765100 [Microsoft-Quic][S][TX][-] SR 883799d98d6f0ecfbcf1f6a36c7a02b6

How can client get notified of this error state on server so that it can stop sending and retry the connection?

[ashish284]

ConnectionShutdown call was missing from my cleanup code, after adding it, client is getting notified when server exits for the first time (2)