Using the Redirector :: Key Features

Server Connection Recovery

The redirector can be configured to attempt to re-establish connection to the server if the connection fails. The Restore Failed Connections option enables this feature.  The Keep-Alive Interval and Maximum Connection Recovery Interval options affect how it works.

By default, the redirector will attempt to re-connect to the server immediately (10ms) after that failed connection is detected. If that attempt is unsuccessful, it will attempt to reconnect on this schedule:

2nd:    1 second

3rd:     2 seconds (+/- 20%)

4th:     4 seconds (+/- 20%)

5th:     8 seconds (+/- 20%)

6th:    16 seconds (+/- 20%)

7th+:  30 seconds (+/- 20%)

Detection of the failed connection may be lengthy if the application is not currently sending data.  TCP/IP connections do not automatically detect a failed connection if there is no traffic.

If the server supports the COM Port Control protocol, the redirector periodically sends a "keep-alive" message to the server so that a failed connection will be revealed.  This message does not affect the redirector-server data stream. The message interval is set by the advanced option Keep-Alive Interval, which defaults to 60 seconds. details

The Maximum Connection Recovery Interval allows you to modify the maximum amount of time that the redirector will wait between connection attempts.  This interval is set by the advanced option Maximum Connection Recovery Interval, which defaults to 30000ms (30 seconds).  details

Changing this setting to 3000ms (3 seconds) would produce the following reconnection schedule:

1st:       10ms

2nd:      1 second

3rd:       2 seconds (+/- 20%)

4th+:     3 seconds (+/- 20%)

Typically this setting is used to force the redirector to try to connect at a short interval, however, it can also be used to increase the interval to longer periods of times than 30 seconds.