7.5. Known Issues with Instance Lifecycle

7.5.1. RECOVER_INSTANCE_STATE_CONSISTENCY setting not fully supported by RTI Infrastructure Services

The RECOVER_INSTANCE_STATE_CONSISTENCY option in the instance_state_consistency_kind field, in the RELIABILITY QoS policy, is not fully supported by the RTI Infrastructure Services products.

RTI Routing Service inputs cannot route instance state transitions from NOT_ALIVE_NO_WRITERS to ALIVE after regaining liveliness with a DataWriter. However, a Routing Service output DataWriter can be configured to use the RECOVER_INSTANCE_STATE_CONSISTENCY setting and respond to matching DataReaders if they request instance state updates after a reconnection.

Persistence Service, Queuing Service, Recording Service, and Replay Service do not support being configured with the RECOVER_INSTANCE_STATE_CONSISTENCY setting, since they do not support storing or publishing ALIVE instance state transitions with no associated data.

[RTI Issue ID CORE-13337]

7.5.2. Persistence Service DataReaders ignore serialized key propagated with dispose updates

Persistence Service DataReaders ignore the serialized key propagated with dispose updates. Persistence Service DataWriters cannot propagate the serialized key with dispose, and therefore ignore the serialize_key_with_dispose setting on the DataWriter QoS.

[RTI Issue ID PERSISTENCE-221]

7.5.3. instance_state_consistency_kind QoS cannot be modified before containing entity is enabled

The instance_state_consistency_kind field in the RELIABILITY QoS policy cannot be modified once the containing DDS entity is created, even if the containing entity is created disabled. Trying to modify the QoS setting in this case will result in the set_qos operation returning DDS_RETCODE_IMMUTABLE_POLICY and an error message being logged.

[RTI Issue ID CORE-13349]