You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS:Ubuntu 22.04
SignalR Server: .net8.0
SignalR.Client 7.0.10
I use SignalR server to push messages to SignalR, but when there are many SignalR clients, it is easy for the SignalR client to be unable to connect to the SignalR server. This situation is easy to occur when the number of client connections exceeds 2000. I suspect it is related to the excessive number of client connections. I wonder if there is any recommended configuration for this?
Due to special circumstances, distribution is not supported for the time being, and only one SignalR server can be used, so I hope it can support more client connections
By adding logs, it was found that an error occurred when the client sent a message to the server. The error message was:
Exception:System.TimeoutException: Server timeout (30000.00ms) elapsed without receiving a message from the server.
at Microsoft.AspNetCore.SignalR.Client.HubConnection.InvokeCoreAsyncCore(String methodName, Type returnType, Object[] args, CancellationToken cancellationToken)
at Microsoft.AspNetCore.SignalR.Client.HubConnection.InvokeCoreAsync(String methodName, Type returnType, Object[] args, CancellationToken cancellationToken)
OS:Ubuntu 22.04
SignalR Server: .net8.0
SignalR.Client 7.0.10
I use SignalR server to push messages to SignalR, but when there are many SignalR clients, it is easy for the SignalR client to be unable to connect to the SignalR server. This situation is easy to occur when the number of client connections exceeds 2000. I suspect it is related to the excessive number of client connections. I wonder if there is any recommended configuration for this?
Due to special circumstances, distribution is not supported for the time being, and only one SignalR server can be used, so I hope it can support more client connections
The server's CPU and memory are both below 20%, and the bandwidth performance is good.
The text was updated successfully, but these errors were encountered: