Download User`s Manual - Community RTI Connext Users

Transcript
33.4.6.1 Connection Liveliness
33.4.6.1 Connection Liveliness
The connection_liveliness property configures the connection liveliness feature. When enabled, the TCP
Transport plugin will periodically exchange some additional control traffic (liveliness requests/responses)
over one of the connections between the TCP Client and Server. This traffic allows determining if a that
connection is not alive anymore, and thus proceed to its close. This avoids depending on the OS notification about the status of the connection, potentially decreasing the time to reestablish lost connections.
The following parameters can be configured:
l
l
l
connection_liveliness.enable: Enables or disables the feature.
connection_liveliness.lease_duration: In seconds, the timeout by which the connection liveliness
must be asserted or the connection will be considered not alive. It is also used also as the period
between connection liveliness checks. Therefore, the maximum time before a connection is marked
as not alive is 2*connection_liveliness.lease_duration.
connection_liveliness.assertions_per_lease_duration: The number of liveliness requests send per
each lease duration. Increasing this value will increase the overhead send into the network, but it
will also make the connection liveliness mechanism more robust.
This feature relies on the creation on an additional thread in the TCP Transport Plugin (the event thread).
For more information about how to configure this thread, see the event_thread in Table 33.1 Properties
for NDDS_Transport_TCPv4_Property_t.
Enabling this feature breaks backwards compatibility with TCP Transport plugins that do not
include this feature.
1015