|
RTI Connext Traditional C++ API Version 7.1.0
|
Specifies and configures the mechanism that allows DDSDataReader entities to detect when DDSDataWriter entities become disconnected or "dead.". More...
Public Attributes | |
| DDS_LivelinessQosPolicyKind | kind |
| The kind of liveliness desired. More... | |
| struct DDS_Duration_t | lease_duration |
| The duration within which a DDSDataWriter must be asserted, or else it is assumed to be not alive. More... | |
| DDS_Long | assertions_per_lease_duration |
| The number of assertions a DDSDataWriter will send during a its DDS_LivelinessQosPolicy::lease_duration. More... | |
Specifies and configures the mechanism that allows DDSDataReader entities to detect when DDSDataWriter entities become disconnected or "dead.".
The liveliness status of a DDSDataWriter is used to maintain instance ownership in combination with the setting of the OWNERSHIP policy. The application is also informed via DDSListener when an DDSDataWriter is no longer alive.
A DDSDataWriter commits to signalling its liveliness at intervals not to exceed the DDS_LivelinessQosPolicy::lease_duration configured on the DDSDataWriter. The rate at which the DDSDataWriter will signal its liveliness is defined by DDS_LivelinessQosPolicy::assertions_per_lease_duration.
The DDSDataReader lease_duration specifies the maximum period at which matching DataWriters must have their liveliness asserted.
In addition, in the subscribing application Connext DDS uses an internal thread that wakes up at the period set by the DataReader's lease_duration to see if a DataWriter lease_duration has been violated.
Important: A DataReader will consider a DataWriter not alive if the DataWriter does not assert its liveliness within the DataWriter lease_duration not the DataReader lease_duration.
Listeners are used to notify a DDSDataReader of loss of liveliness and DDSDataWriter of violations to the liveliness contract. The on_liveliness_lost() callback is only called once, after the first time the lease_duration is exceeded (when the DDSDataWriter first loses liveliness).
This QoS policy can be used during system integration to ensure that applications have been coded to meet design specifications. It can also be used during runtime to detect when systems are performing outside of design specifications. Receiving applications can take appropriate actions in response to disconnected DataWriters.
This policy controls the mechanism and parameters used by RTI Connext to ensure that particular DataWriters on the network are still alive. The liveliness can also affect the ownership of a particular instance, as determined by the OWNERSHIP policy.
This policy has several settings to support both data types that are updated periodically as well as those that are changed sporadically. It also allows customisation for different application requirements in terms of the kinds of failures that will be detected by the liveliness mechanism.
The DDS_AUTOMATIC_LIVELINESS_QOS liveliness setting is most appropriate for applications that only need to detect failures at the process-level, but not application-logic failures within a process. RTI Connext takes responsibility for renewing the leases at the required rates and thus, as long as the local process where a DDSDomainParticipant is running and the link connecting it to remote participants remains connected, the entities within the DDSDomainParticipant will be considered alive. This requires the lowest overhead.
The manual settings (DDS_MANUAL_BY_PARTICIPANT_LIVELINESS_QOS, DDS_MANUAL_BY_TOPIC_LIVELINESS_QOS) require the application on the publishing side to periodically assert the liveliness before the lease expires to indicate the corresponding DDSEntity is still alive. The action can be explicit by calling the DDSDataWriter::assert_liveliness operation or implicit by writing some data.
The two possible manual settings control the granularity at which the application must assert liveliness.
Changes in LIVELINESS must be detected by the Service with a time-granularity greater or equal to the DDS_LivelinessQosPolicy::lease_duration. This ensures that the value of the DDS_LivelinessChangedStatus is updated at least once during each lease_duration and the related Listeners and DDSWaitSet s are notified within a lease_duration from the time the LIVELINESS changed.
The value offered is considered compatible with the value requested if and only if the following conditions are met:
lease_duration <= requested lease_duration evaluates to DDS_BOOLEAN_TRUE. | DDS_LivelinessQosPolicyKind DDS_LivelinessQosPolicy::kind |
The kind of liveliness desired.
[default] DDS_AUTOMATIC_LIVELINESS_QOS
| struct DDS_Duration_t DDS_LivelinessQosPolicy::lease_duration |
The duration within which a DDSDataWriter must be asserted, or else it is assumed to be not alive.
For a DataWriter, the lease_duration specifies a timeout by which liveliness must be asserted for the DataWriter or the DataWriter will be considered inactive or not alive.
For a DataReader, the lease_duration specifies the maximum period at which the DataReader will check to see if the matching DataWriters are still alive according to the DataWriters lease_duration value.
Important: A DataReader will consider a DataWriter not alive if it does not assert its liveliness within the DataWriter lease_duration not the DataReader lease_duration.
[default] DDS_DURATION_INFINITE
[range] [0,1 year] or DDS_DURATION_INFINITE
| DDS_Long DDS_LivelinessQosPolicy::assertions_per_lease_duration |
The number of assertions a DDSDataWriter will send during a its DDS_LivelinessQosPolicy::lease_duration.
This field only applies to a DDSDataWriter and is not considered during QoS compatibility checks.
The default value is 3. A higher value will make the liveliness mechanism more robust against packet losses, but it will also increase the network traffic.
[default] 3
[range] [2, 100 million]