Menu
We have come across this link which specifies the different time out properties: https://github.com/SignalR/SignalR/wiki/Configuring-SignalR
And also this excellent post (When does a reconnect in signalR occour?) on how disconnections and reconnections happen between a SignalR client and a SignalR server.
Just to re-iterate the different situations from the above post:
"A hub reconnect occurs when a client goes offline then regains connectivity shortly after. SignalR configuration values largely determine the time stamps of the following examples so do not take the times verbatim.
Here are several examples and their outcomes (time format m:ss) involving reconnecting behavior:
Situation 1
0:00 - Client connects to server, OnConnected is triggered
0:10 - Client loses connection due to ISP issues (and realizes it loses connection)
0:15 - Client Regains connectivity
0:16 - OnReconnected event is triggered
Situation 2
0:00 - Client connects to server, OnConnected is triggered
0:10 - Client loses connection due to pulling ethernet cable (doesn't realize it's disconnected)
0:15 - Client Regains connectivity
Two things can happen here
A: 0:16 - Nothing happens and client continues on with its previous connection
B: 0:~45 - Client Realizes its disconnected *
B: 0:46 - Client transitions into the reconnecting state
B: 0:47 - Client successfully reconnects and the OnReconnected event is triggered.
Situation 3
0:00 - Client connects to server, OnConnected is triggered
0:10 - Client loses connection due to pulling ethernet cable (doesn't realize it's disconnected)
0:~45 - Client Realizes its disconnected *
0:46 - Client transitions into the reconnecting state
1:15 - Server determines that client has been gone for too long and then forgets about it, queuing up a "disconnect" command for the client to receive if it reconnects slightly later. ***
1:15 - OnDisconnect is triggered 1:16 - Client regains connectivity
1:17 - Client does a "soft" reconnect (does not trigger OnReconnected)
1:18 - Client retrieves the "disconnect" command
1:19 - Client calls "stop" and does a soft disconnect (does not trigger OnDisconnected)
Situation 4
0:00 - Client connects to server, OnConnected is triggered
0:10 - Client loses connection due to pulling ethernet cable (doesn't realize it's disconnected)
0:~45 - Client Realizes its disconnected *
0:46 - Client transitions into the reconnecting state
1:15 - Server determines that client has been gone for too long and then forgets about it, queuing up a "disconnect" command for the client to receive if it reconnects slightly later. ***
1:15 - OnDisconnect is triggered 1:30 - Client stops trying to reconnect (been trying too long) **
1:30 - Client transitions into disconnected state
** Due to client side disconnect timeout: Used to determine when a client has been reconnecting for too long of a period and chances are the server has forgotten about the client during the time
*** Due to server disconnect timeout: Used to determine when a client should be forgotten about. It's a time span that starts accruing once a connection is tagged as dead on the server. Ultimately the server queues a disconnect command for the client's topic which tells the client (if it reconnects) that it needs to start a fresh connection. The command will disappear from the server when the topic is cleaned up."
What we are finding is that we get disconnects and reconnects quite often (1 and 2 above) between a .NET SignalR client and an ASP.NET MVC SignalR server, and also disconnects that do not result in reconnections (3 and 4 above). We know that ServerSentEvents protocol is being used.
It is hard to know what timeout properties we need to tweak (increase or decrease) to:
An important thing to note here is that our .NET SignalR Client is actually a windows service which is connected to the server all the time.
We have currently just kept the defaults, which are:
Also, we are using SignalR 1.0.1.
446
Timeout configuration for SignalR can be set in Application_Start method of Global class in Global. asax. cs file. // Wait a maximum of 30 minutes after a transport connection is lost // before raising the Disconnected event to terminate the SignalR connection.
The default keepalive timeout period is currently 20 seconds. If your client code tries to call a Hub method while SignalR is in reconnecting mode, SignalR will try to send the command. Most of the time, such attempts will fail, but in some circumstances they might succeed.
hub. stop(). done(function() { alert('stopped'); });
The .NET client does NOT have this behavior yet. and it will not reconnect if the client suddenly drops a connection. It will in 1.1.
186
Your timeouts are properly set. In the current release there is no client side keep alive for the .net client to ensure that the client maintains connectivity.
In the next release you will have a .net client side keep alive. If you're willing to work with a dev build of the project the feature is currently available on the dev branch https://github.com/SignalR/SignalR/tree/dev.
Also for reference, here's the issue related to what you're seeing https://github.com/SignalR/SignalR/issues/741.
23
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
