Managing Connection Failure - Wiki
Wiki
Managing Connection Failure
KeepAlive#
In order to rapidly detect connection failures, the Etch KeepAlive message filter periodically checks the health of the client-server connection and resets it if it is not responsive. By default, KeepAlive messages are 15 seconds apart and if four KeepAlive messages fail, the connection is reset.
To Enable KeepAlive#
KeepAlive is enabled at the server by default. You must append the KeepAlive filter to the Connection URI in your client applications and plugins for them to work properly.
For example, if your Connection
String uri = "tls://localhost:4001?TlsConnection.authReqd=false";
Append the KeepAlive filter like so:
String uri = "tls://localhost:4001?TlsConnection.authReqd=false&filter=KeepAlive";
To Modify KeepAlive Parameters#
The KeepAlive filter has two parameters: KeepAlive.Delay and KeepAlive.Count. Delay controls the number of seconds between KeepAlive messages and Count controls the number of messages sent before the connection is reset. By default, KeepAlive messages are 15 seconds apart and if four KeepAlive messages fail, the connection is reset. You can reset them by modifying the Connection URI to override the defaults.
For example, the folllowing URI sets the Delay to 20 seconds and the Count to 5.
String uri = "tls://localhost:4001?TlsConnection.authReqd=false&filter=KeepAlive&KeepAlive.Delay=20000&KeepAlive.Count=5";
To Disable KeepAlive#
- Open C:\Program Files\Cisco Systems\Unified Application Environment\AppServer\AppServerService.exe.config.
- Set "EtchBridgeKeepAliveDelay" value to "0".
- Restart the AppServer service.