10.4.20. Interoperability¶

10.4.20.1. [Critical] Failure to ignore vendor-specific PIDS¶

Connext Micro would not ignore vendor-specific parameter IDs (PIDs) when deserializing data from other DDS vendors.

[RTI Issue ID MICRO-12271]

10.4.20.2. [Critical] NULL pointer access in AUTOSAR Classic when a ping message received from Connext Professional 7.3.0 or higher¶

An AUTOSAR Classic application using Connext Micro caused a NULL pointer access if a ping message was received from an application using Connext Professional 7.3.0 or higher.

[RTI Issue ID MICRO-7860]

10.4.20.3. [Major] KeyFlag for fragmented data interpreted incorrectly¶

The KeyFlag (or K-bit) for fragmented data was interpreted from the wrong position and was always ignored.

[RTI Issue ID MICRO-11460]

10.4.20.4. [Major] Samples of mutable types may have been dropped when bit FLAG_MUST_UNDERSTAND was set on key members¶

Connext Micro may have failed to deliver samples to applications, and reported them as lost, when receiving data on a Topic whose type:

Had mutable extensibility;
Derived from another type;
Had at least one member marked as a key.

The failure would be triggered if the sending node set the bit FLAG_MUST_UNDERSTAND of the parameter IDs preceding each key member value in the serialized payload, as prescribed by the OMG ‘Extensible and Dynamic Topic Types for DDS’ specification.

This error may have only manifested in a cross-vendor interoperability scenario where Connext received data from a different vendor’s DDS implementation. The error could also have been triggered if receiving data from a type with members marked as “must understand,” for which the specification also requires the bit FLAG_MUST_UNDERSTAND be set in their serialized parameter IDs. Support for “must understand” members is introduced in this release. See Must-Understand Members in the RTI Connext Core Libraries Extensible Types Guide for more information.

Connext Micro will now correctly deliver all samples on Topics whose type may have triggered this error.

Note: To maximize interoperability with previous releases, Connext Micro does not set FLAG_MUST_UNDERSTAND for key members of mutable types by default. You can change this default and force compliance with the specification by using the Extensible Types Compliance Mask.

[RTI Issue ID MICRO-12758]