SignalR improve connection close experience

[BrennanConroy]

• Flow more exceptions to OnDisconnectedAsync Always call Hub.OnDisconnectedAsync with an Exception when a client disconnects ungracefully #26701
• Investigate SendBeacon Investigate using sendBeacon to trigger disconnect on browser close for non-websocket transports #14847
• Improve error logs
  • Browser can use ResponseType Use Response.Type in TS client to provide better error messages #26636
  • Some logs look almost identical on client and server would be nice to more easily differentiate them
  • If something errors can we provide suggestions for what is wrong?
• Add more to the troubleshooting doc https://docs.microsoft.com/en-us/aspnet/core/signalr/troubleshoot?view=aspnetcore-3.1
• 404 errors Improve error messaging for 404s #5350

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[aleksandar-manukov]

Hi,

I am not sure if this is the correct place to ask, but we have a problem related to closing the SignalR connection. The problem is with StopAsync method of the HubConnection class of the SignalR Core .NET client. After migrating to version 5.0.0 of the client it takes several seconds for the method to complete (between 5 and 10 seconds). In order to not wait several seconds we make a fire-and-forget workaround:

Task.Run(async () =>
{
    // This try catch is in any case in order to not have any unhandled exception while stopping the connection.
    try
    {
        try
        {
            await _hubConnection.StopAsync();
        }
        finally
        {
            await _hubConnection.DisposeAsync();
        }
    }
    catch
    {
    }
});

Do you know if this workaround could lead to some open connections left? And is this planned to be fixed soon?

Thanks in advance!

[BrennanConroy]

I am not sure if this is the correct place to ask

It isn't, please file a new issue

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.