4. What’s Fixed in 7.5.0

This section describes bugs fixed in Connext 7.5.0. These are fixes since 7.4.0.

RTI® Connext® 7.5.0 is an early access release. See the Connext Releases page on the RTI website for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

[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.

4.1. Data Corruption

4.1.1. [Critical] Persistence Service had a race condition when used as a library

When Persistence Service was used as a library and more than one instance of Persistence Service was created in the same process, it could have suffered a race condition upon initialization. This race condition prevented a global mutex object from being correctly initialized, which could have affected the rest of the execution of all services.

[RTI Issue ID PERSISTENCE-378]

4.1.2. [Critical] Unexpected sample losses and error messages when enabling sample logging

Enabling sample logging in a persistence group by setting <persistence_group>/<sample_logging>/<enable> to true may have caused unexpected sample losses and errors like the following:

ERROR [0x01018498,0xF3977805,0x85BB4E38:0x80000002{Entity=DW,Topic=Example Topic,Type=ServiceType,Domain=0}|UNREGISTER] WriterHistoryOdbcPlugin_addSample:FAILED TO FIND | Instance with keyhash (16)c9a904273592c13adccc940303ea2c30
ERROR PERSISTENCEServiceTopic_writeSample:!unregister
ERROR PERSISTENCEServiceTopic_runWrite:!write sample
ERROR [0x01018498,0xF3977805,0x85BB4E38:0x80000002{Entity=DW,Topic=Example Topic,Type=ServiceType,Domain=0}|UNREGISTER] WriterHistoryOdbcPlugin_addSample:FAILED TO FIND | Instance with keyhash (16)c9a904273592c13adccc940303ea2c30
ERROR PERSISTENCEServiceTopic_writeSample:!unregister
ERROR PERSISTENCEServiceTopic_runWrite:!write sample

This problem only applied to keyed topics.

[RTI Issue ID PERSISTENCE-391]

4.2. Hangs

4.2.1. [Critical] Persistence Service may have frozen when using a WaitSet and service failed to start

Persistence Service froze if using a WaitSet and the service failed to start (for example, due to an invalid configuration).

[RTI Issue ID PERSISTENCE-390]

4.2.2. [Critical] Potential deadlock when processing a remote stop command

A potential deadlock occurred when attempting to stop a Persistence Service instance by sending a remote stop command.

[RTI Issue ID PERSISTENCE-373]

4.3. Memory Leaks/Growth

4.3.1. [Major] Persistence Service could leak memory if it failed to initialize

When Persistence Service experienced an error upon initialization, it could fail to free some memory, resulting in a leak.

[RTI Issue ID PERSISTENCE-376]

4.4. Other

4.4.1. [Major] Monitoring 2.0 not enabled for Persistence Service as a Library via XML Profile

Enabling Monitoring 2.0 through an XML profile did not work when using Persistence Service as a library. Despite the correct loading of the USER_QOS_PROFILES.xml file, Monitoring 2.0 was not activated for the Persistence Service participants. This issue was specific to using Persistence Service as a library and did not affect other services such as using Routing Service as a library.

[RTI Issue ID PERSISTENCE-382]