That would have very poor performance, as each individual timer produces significant load on the system. We don't just start a timer for the duration you provide and then send the keep-alive when that timer elapses. The default value for the timeout is 30 seconds and the keep-alive interval is 15 seconds (it's generally important for the server timeout to be at least double the keep-alive interval to make sure there's time to receive a keep-alive frame)Īnother thing to keep in mind is that the timeout values are not strict values used in timers. ![]() Good catch! I submitted dotnet/AspNetCore.Docs#7906 to fix that. The documentation lacks info about the default value You could also use those timestamps to help determine if there's a network issue. Increasing the logging to Trace on the server would also give you log messages whenever the server sends a ping. It looks like there is a REST API to do it, but I don't have experience with that. I don't know if it's possible to collect network traces from Azure Web Apps. Then the timestamps could tell you what latency might exist in the system. Especially if you're able to get data regarding the same connection from both the client and the server. Getting network trace data would definitely help. HubConnection.ServerTimeout = TimeSpan.FromSeconds(6) v 1.0.0 ( Just updated to 1.0.2 I'll keep testing and come up with feedback) What should I look for in server side logs to see that KeepAlive message have been sent correctly? I see in Fiddler that KeepAlive (Type: 6 messages) sometimes come at 4 seconds instead of 3.Ĭould some long-running code on the web app to delay the KeepAlive sending? As I wrote below I don't have any network traces yet, but as soon as I will have something, I'l post here.Īlthough I set Always On for WebApp on Azure sometimes I see request response delays. ![]() Misconfigured SignalR server/client (please Help!).So I kind of excluding Client side errors. ![]() I have 2 clients and they both get disconnected simoultaneously. System.TimeoutException: Server timeout (6000.00ms) elapsed without receiving a message from the server. Connection is shutting down due to an error. Only meaningful log I get is on client side complaining the server did not send a message: They are very short (under 1 minute, and tipically below 10 s) and appear at irregular intervals (online: 1h, offline: 2 s, online: 30 min, offline 2s and so on) I cannot make a whole day without some disconnects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |