Last post Dec 29, 2013 01:48 PM by Duane56
Dec 29, 2013 01:48 PM|Duane56|LINK
Any thoughts on this, anyone? Is "MinByptesPerSecond" errors in fact the expected result if using the IIS default minByptesPerSecond of 240 and SignalR ConnectionTimeout default of 110 when longPolling?
Hi, fabulous job SignalR team, exciting stuff!
Problem, I've got some JS longPolling clients (mobile Android/PhoneGap) that can't keep a connection live at default timeout settings, apparently because the server will terminate the connection due to "Timer_MinBytesPerSecond" errors?
From the server log:
/signalr/signalr/reconnect?transport=serverSentEvents&connectionToken=[...]&messageId=[...]&connectionData=[...] - 68298 Timer_MinBytesPerSecond customerPool_xxx
From the client log (with ConnectionTimeout set to 60 seconds):
[11:54:02 ...] SignalR: Opening long polling request to 'http://[...]/signalr/poll?transport=longPolling&connectionToken=[...]&groupsToken=[...]&messageId=[...]&connectionData=[...]'.
[11:54:49 ...] SignalR: An error occurred using longPolling. Status = error. Response = \n Service Unavailable. \n Technical description: 504 Gateway Time-out - The web server is not responding \n
[11:54:49 ...] SignalR error: Error: Long polling request failed.
[11:54:52 ...] SignalR: Opening long polling request to 'http://[...]/signalr/reconnect?transport=longPolling&connectionToken=[...]&groupsToken=[...]&messageId=[...]&connectionData=[...]'.
[11:54:53 ...] SignalR: Raising the reconnect event
[above error/reconnect events repeat a total of 5 times, then...]
[11:58:43 ...] SignalR: Couldn't reconnect within the configured timeout (30000ms), disconnecting.
[11:58:43 ...] SignalR: Stopping connection.
[11:58:43 ...] SignalR: Aborted xhr request.
Through trial-and-error I've found that I can set the ConnectionTimeout all the way down to 30 seconds and reliably keep a connection live withoug the MinBytesPerSecond errors, but I'd much rather be able to use timeouts closer to the 110 default due to
concerns about 1) frequent reconnects possibly increasing battery drain, and 2) possible message loss.
1) are those concerns valid?
2) is there any other work around?
I know theoretically the MinFileBytesPerSecond setting can be changed or disabled on IIS, but I'm using a hosted server (IIS 8/.NET 4.5) and they won't even entertain the idea of altering this setting due to (understandable?) concerns over security and/or
effects on other sites on the server.
Any help and/or insight would be greatly appriciated! Thanks, have a great day!