6. Known Issues

Note

For an updated list of critical known issues, see the Critical Issues List on the RTI Customer Portal at https://support.rti.com.

6.1. Coherent Changes not Propagated as Coherent Set

Persistence Service will propagate the samples inside a coherent change. However, it will propagate these samples individually, not as a coherent set.

6.2. TopicQueries not Supported in PERSISTENT Mode

Getting TopicQuery data from a Persistence Service instance configured to store data on disk is not currently supported.

Note

Getting TopicQuery data from a Persistence Service instance running in TRANSIENT (storing data in memory) mode is supported.

[RTI Issue ID PERSISTENCE-143]

6.3. <comm_ports> not Supported when Using Real-Time WAN Transport

Persistence Service can use the RTI Real-Time WAN Transport. However, the port configuration using <comm_ports> or the property dds.transport.UDPv4_WAN.builtin.comm_ports is not currently supported by Persistence Service.

[RTI Issue ID PERSISTENCE-206]

6.4. 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]

6.5. Some tags in the XML configuration must be grouped in a strict order

The XML validator tools Persistence Service uses to validate XML configuration files adhere to the XML 1.0 specification, which doesn’t offer a way of defining collections of unordered tags that are both bounded and unbounded in occurrences.

This limitation is no longer present in XML 1.1. However, there are no C or C++ validators compliant with the XML 1.1 specification at the time of writing.

[RTI Issue ID CORE-14178]