Stale Connection Recovery is a feature supported by the TCP Server and JavaScript TCP Server communication points when operating in a single connection mode (that is, the Number of Connections configuration property has been set to 1). It can be used to re-establish a silently dropped connection without requiring a restart of the communication point.
When TCP connections are silently dropped without undergoing the full connection termination phase, the TCP Server and JavaScript TCP Server communication points still count the connection towards their maximum number of connections. This can lead to the communication points having to be manually restarted for a TCP client to be able to reconnect. The Stale Connection Recovery options allow Rhapsody to treat a connection that has been idle for the specified time period as stale. If a new connection request is received while the existing connection is stale then the stale connection will be closed and the new connection will be established.
These options are not available when the TCP Server or JavaScript TCP Server communication points allow multiple connections, as in that case the new connection can be established immediately, and the Idle Timeout configuration property used to eventually drop the stale connections.
This option should only be enabled if absolutely required, and never on a public facing server, as it could potentially be used to denial of service the expected client by repeating causing its connection to be dropped.
Stale Connection Recovery is configured using the following configuration properties:
| Property | Description |
|---|---|
| Stale Connection Recovery | Whether to enable Stale Connection Recovery:
This setting only takes effect if the Number of Connections configuration property is set to |
| Stale Connection Timeout | The idle timeout in seconds after which a connection is regarded as stale and so replaceable if a new connection is established. |