Hi,
I'm seeing timeouts for an element that is configured with Number of retries set to 3, but it only attempts the command once before timing out.
The element total timeout setting is 30 seconds, and the single command setting is 10 seconds.
I see the intial single HTTP command time out after 10 seconds as expected, then 30 seconds later the element will time out, but with no retry in between.
The element log only shows the alarm state switching to timeout, with no details on failed commands. The SLProtocol and SLWatchdog logs show nothing relating to the timeout either.
How is it possible that the command isn't being retried before the element times out?
Thanks
Hi Thomas,
What does the Stream Viewer show?
This note provides more info on when retries will be executed with HTTP communication:
A retry mechanism (as configured in the element connection settings) is triggered when an HTTP request times out (i.e., upon reception of the WINHTTP_ERROR_TIMEOUT error) and when the SLPort process is unable to connect to the web server (i.e., upon reception of the ERROR_WINHTTP_CANNOT_CONNECT error).
Also in case of the following a retry should be performed: ERROR_WINHTTP_SECURE_FAILURE, SEC_E_BUFFER_TOO_SMALL).
If the Stream Viewer shows any of these, a retry should normally be performed.
Does the connector that is executed by the element only have a single connection or does it have multiple?
Hi Pedro,
Thanks for getting back to me.
After opening a support case, I've learnt that the error I was seeing in Stream Viewer – ERROR_WINHTTP_CONNECTION_ERROR – does _NOT_ trigger a retry like I assumed it would.
When this device is overloaded, it drops HTTP connections instead of letting them timeout.
This is why I wasn't seeing the expected retries.