6.2.1. RTI Connext Core Libraries

The following issues affect backward compatibility in the Core Libraries starting in Release 6.0.1.

6.2.1.1. Durable Writer History properties prefix must contain “.builtin” substring

In 6.0.0, you could configure the Durable Writer History properties in two different ways:

  • Without using the .builtin substring: for example, dds.data_writer.history.odbc_plugin.driver

  • Using the .builtin substring: for example, dds.data_writer.history.odbc_plugin.builtin.driver

By default, not using .builtin generates a WARNING in 6.0.1 and an ERROR in 6.1.0 and later releases. For example, if you try to use the Durable Writer History properties without .builtin in 6.1.0, you will get an error similar to the error below, and DataWriter creation will fail. In 6.0.1 you will get warnings, but DataWriter creation will be successful.

ERROR [0x0101B794,0x7E4E17F1,0x31DC168E:0x80000008{Entity=Pu,Domain=56}|CREATE DW WITH TOPIC Raw1kTopic] DDS_PropertyQosPolicy_validateEntityPropertyNames:Unexpected property: dds.data_writer.history.odbc_plugin.driver. Closest valid property: dds.data_writer.history.odbc_plugin.builtin.driver. If you wish to proceed with this property name anyway, change 'dds.participant.property_validation_action' to 'VALIDATION_ACTION_SKIP' or 'VALIDATION_ACTION_WARNING'.
ERROR [0x0101B794,0x7E4E17F1,0x31DC168E:0x80000008{Entity=Pu,Domain=56}|CREATE DW WITH TOPIC Raw1kTopic] DDS_DataWriterQos_is_consistentI:inconsistent QoS property
ERROR [0x0101B794,0x7E4E17F1,0x31DC168E:0x80000008{Entity=Pu,Domain=56}|CREATE DW WITH TOPIC Raw1kTopic] DDS_Publisher_create_datawriter_disabledI:ERROR: Inconsistent QoS
ERROR [0x0101B794,0x7E4E17F1,0x31DC168E:0x80000008{Entity=Pu,Domain=56}|CREATE DW WITH TOPIC Raw1kTopic] DDS_Publisher_create_datawriter:CREATION FAILURE | DataWriter

Although it is strongly recommended to use the .builtin substring, you can get the old (6.0.0) behavior back by skipping property validation (using VALIDATION_ACTION_SKIP), as described in the “Property Validation” section of PROPERTY QosPolicy, in the RTI Connext Core Libraries User’s Manual.

Note

The section How To Configure Durable Writer History, in the RTI Connext Core Libraries User’s Manual, and Persistence Service API Reference still describe the Durable Writer History properties without the .builtin substring. These are documentation errors, which are fixed in release 7.1.0.

[RTI Issue ID CORE-12240]

6.2.1.2. Durable Writer History properties cannot be set on DomainParticipant

In 6.0.0, you could configure the Durable Writer History properties on the DomainParticipant so they would be applied to all DataWriters belonging to the DomainParticipant.

Now, by default, setting the properties at the DomainParticipant level generates a WARNING in 6.0.1 and an ERROR in 6.1.0 and later releases. For example, if you try to use the Durable Writer History properties in 6.1.0, you will get an error similar to the error below, and DomainParticipant creation will fail. In 6.0.1, you will get warnings, but DomainParticipant creation will be successful.

ERROR [CREATE DP|LC:DISC]DDS_PropertyQosPolicy_validateEntityPropertyNames:Unexpected property: dds.data_writer.history.odbc_plugin.builtin.driver. Closest valid property: dds.data_writer.history.plugin_name. If you wish to proceed with this property name anyway, change 'dds.participant.property_validation_action' to 'VALIDATION_ACTION_SKIP' or 'VALIDATION_ACTION_WARNING'.
ERROR [CREATE DP|LC:DISC]DDS_DomainParticipantQos_is_consistentI:inconsistent QoS property
ERROR [CREATE DP|LC:DISC]DDS_DomainParticipantFactory_create_participant_disabledI:ERROR: Inconsistent QoS

You can get the old (6.0.0) behavior back by skipping property validation (using VALIDATION_ACTION_SKIP), as described in the “Property Validation” section of PROPERTY QosPolicy, in the RTI Connext Core Libraries User’s Manual.

[RTI Issue ID CORE-13516]