5.6. What’s Fixed in 7.0.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.6.1. [Critical] Fatal error when persisting unkeyed Topics upon restore or IP mobility event
Persistence Service generated the following fatal error and shut down when persisting unkeyed Topics if all of the following conditions were met:
<use_durability_service> was set to true in the <persistence_group> OR <writer_qos>/<writer_data_lifecycle>/<autopurge_disposed_instances_delay> was set to zero in the <persistence_group>
<writer_in_memory_state> was set to false in the <persistence_group>.
There was an IP mobility event (for instance, an interface went down) OR Persistence Service was started with the
-restorecommand-line option set to true.
The error backtrace was as follows:
#4 WriterHistoryOdbcPlugin_logAndCheckODBCError ??:? [0x31590B]
#5 WriterHistoryOdbcPlugin_handleODBCError ??:? [0x315CE5]
#6 WriterHistoryOdbcPlugin_beginDisposedInstanceIteration ??:? [0x34B202]
This problem has been resolved.
[RTI Issue ID PERSISTENCE-255]
5.6.2. [Major] Samples published out of order from same virtual GUID were dropped
If Persistence Service received samples for a given virtual GUID with sequence numbers out of order, Persistence Service dropped samples with sequence numbers lower than the highest received sequence number. This issue has been resolved.
[RTI Issue ID PERSISTENCE-250]
5.6.3. [Minor] Schema files not compliant with DDS-XML specification
The following change has been made to the schema file
rti_persistence_service.xsd, and its included files, to make them
compliant with the DDS-XML specification
(https://www.omg.org/spec/DDS-XML/1.0/PDF):
Renamed <participant_qos> to <domain_participant_qos>
The old tag is still accepted by the Connext XML parser and the XSD schema to maintain backward compatibility.
[RTI Issue ID PERSISTENCE-213]