5.4. What’s Fixed in 7.1.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.4.1. [Major] Persistence Service stored/forwarded samples multiple times when there were two or more equivalent versions of a type for a Topic

Persistence Service stored and forwarded incoming samples multiple times when there were two or more equivalent versions of a type for a given Topic in the system.

Two types are equivalent when they only differ on typedef. For example, MyType and MyType2 are equivalent in this IDL snippet:

struct MyType {
    long m1;
};

typedef long MyLong;

struct MyType2 {
    MyLong m1;
};

This problem has been fixed.

[RTI Issue ID PERSISTENCE-269]

5.4.2. [Major] Unexpected fatal error when number of instances reached the limit *

In 7.0.0, an unexpected fatal error could be logged when the following occurred:

  • Persistence Service was running in PERSISTENT mode.

  • The number of instances reached the max_instances limit set in one of the Persistence Service DataWriters’ RESOURCE_LIMITS QoS.

  • Connext could not find an instance to delete (such as an unregistered one), to replace with the new instance. So the new instance could not be added.

This log message is expected, but it is not a fatal error, so its verbosity has been updated to WARNING, as follows:

WriterHistoryOdbcPlugin_createResources:FIND FAILURE | Instance for replacement

WriterHistoryOdbcPlugin_createResources:FIND FAILURE | Instance for replacement
WriterHistoryOdbcPlugin_addInstance:OUT OF RESOURCES | Exceeded the number of instances. Current registered instances (128), maximum number of instances (128)(writer_qos.resource_limits.max_instances)

[RTI Issue ID CORE-13496]

5.4.3. [Minor] Persistence Service XSD schema was broken *

In release 7.0.0, the Persistence Service XSD schema was broken due to an additional closing tag. This was a regression that only affected the 7.0.0 release. This issue has been fixed.

[RTI Issue ID PERSISTENCE-276]