LivelinessQosPolicy Class Reference

Specifies and configures the mechanism that allows entities to detect when entities become disconnected or "dead.". More...

Inheritance diagram for LivelinessQosPolicy:


List of all members.

Public Attributes

LivelinessQosPolicyKind kind
 The kind of liveliness desired.
final Duration_t lease_duration
 The duration within which a must be asserted, or else it is assumed to be not alive.

Detailed Description

Specifies and configures the mechanism that allows entities to detect when entities become disconnected or "dead.".

Liveliness must be asserted at least once every lease_duration otherwise RTI Connext will assume the corresponding or is no longer alive.

The liveliness status of a is used to maintain instance ownership in combination with the setting of the OWNERSHIP policy. The application is also informed via when an is no longer alive.

A requests that liveliness of writers is maintained by the requested means and loss of liveliness is detected with delay not to exceed the lease_duration.

A commits to signalling its liveliness using the stated means at intervals not to exceed the lease_duration.

Listeners are used to notify a of loss of liveliness and 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 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 run time to detect when systems are performing outside of design specifications. Receiving applications can take appropriate actions in response to disconnected DataWriters.

Changeable = UNTIL ENABLE


This policy controls the mechanism and parameters used by RTI Connext to ensure that particular entities 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 LivelinessQosPolicyKind.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 is running and the link connecting it to remote participants remains connected, the entities within the will be considered alive. This requires the lowest overhead.

The manual settings (LivelinessQosPolicyKind.MANUAL_BY_PARTICIPANT_LIVELINESS_QOS, LivelinessQosPolicyKind.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 is still alive. The action can be explicit by calling the 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 lease_duration. This ensures that the value of the is updated at least once during each lease_duration and the related Listeners and 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:

See also:

Member Data Documentation

The kind of liveliness desired.

[default] LivelinessQosPolicyKind.AUTOMATIC_LIVELINESS_QOS

The duration within which a must be asserted, or else it is assumed to be not alive.


[range] [0,1 year] or

RTI Connext Java API Version 4.5f Copyright © 17 Mar 2012 Real-Time Innovations, Inc