5.2. What’s Fixed in 7.2.0

[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.

5.2.1. [Critical] Segmentation fault issue with Persistence Service and Distributed Logger

Previous releases encountered a segmentation fault when using the Persistence Service library. This issue occurred when attempting to use the Distributed Logger after deleting an RTI_PersistenceService object. The problem occurred because the call to the RTI_PersistenceService_delete operation was deleting the Distributed Logger instance.

This problem is now fixed. If the user application creates the Distributed Logger instance instead of relying on its creation through the <distributed_logger> XML tag by Persistence Service, the deletion of the Persistence Service instance will no longer attempt to delete it.

[RTI Issue ID PERSISTENCE-297]

5.2.2. [Major] Error creating a persistence group DataWriter when setting dds.data_writer.history.odbc_plugin.builtin.sample_cache_max_size to -1

Creating a persistence group DataWriter could fail with the following error if the property dds.data_writer.history.odbc_plugin.builtin.sample_cache_max_size was set to -1 in the <datawriter_qos>:

"!allocate sample buffer pool"

Even if the DataWriter creation did not fail, the value of dds.data_writer.history.odbc_plugin.builtin.sample_cache_max_size would be incorrectly applied. Instead, it would be set to dds.data_writer.history.odbc_plugin.builtin.instance_cache_max_size for keyed topics and 1 for unkeyed topics.

This problem has been resolved.

[RTI Issue ID PERSISTENCE-296]

5.2.3. [Minor] <reader_checkpoint_frequency> may not have been applied correctly

There was an issue applying the configuration parameter <reader_checkpoint_frequency> when the value was different than 1. The desired frequency for storing the PRSTDataReader state might not have been accurately applied, resulting in a delayed storage process. This problem has been resolved.

[RTI Issue ID PERSISTENCE-307]