4.3. Regressions in 7.0.0

The following regressions occur in Connext 7.0.0.

4.3.1. Core Libraries

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

This regression was introduced in 6.0.1, and RTI does not intend to fix it. You must add the .builtin substring to the Durable Writer History properties. See Durable Writer History properties prefix must contain “.builtin” substring in the 6.0.1 Regressions section.

4.3.1.2. Durable Writer History properties cannot be set on DomainParticipant

This regression was introduced in 6.0.1 and is not yet fixed. See Durable Writer History properties cannot be set on DomainParticipant in the 6.0.1 Regressions section.

4.3.1.3. Fixed in 7.1.0

4.3.1.3.1. DomainParticipant with non-default metatraffic_transport_priority QoS does not complete discovery

This regression was introduced in 6.1.0 and has been fixed in 6.1.2 and 7.1.0. See DomainParticipant with non-default metatraffic_transport_priority QoS does not complete discovery in the 6.1.0 Regressions section.

4.3.1.3.2. Broken communication when DataWriter with transport priority discovers DataReader with multicast receive address

This regression was introduced in 6.1.0 and has been fixed in 6.1.2 and 7.1.0. See Broken communication when DataWriter with transport priority discovers DataReader with multicast receive address in the 6.1.0 Regressions section.

4.3.1.3.3. Unexpected precondition error with debug libraries on a reliable DataWriter while sending a GAP

This regression was introduced in 6.1.2 and 7.0.0 and has been fixed in 7.1.0. See Unexpected precondition error with debug libraries on a reliable DataWriter while sending a GAP in the 6.1.1/6.1.2 Regressions section.

4.3.1.3.4. No more than 100 asynchronous publisher threads can be created

This regression was introduced in 6.1.0 and has been fixed in 6.1.2 and 7.1.0. See No more than 100 asynchronous publisher threads can be created in the 6.1.0 Regressions section.

4.3.1.3.5. Creating DynamicDataTypePlugin with TypeCode from discovery and using content filtering causes segmentation fault

This regression was introduced in 6.0.0 and has been fixed in 6.0.1.30, 6.1.2, and 7.1.0. See Creating DynamicDataTypePlugin with TypeCode from discovery and using content filtering causes segmentation fault in the 6.0.0 Regressions section.

4.3.1.3.6. Crash with NULL listeners and non-none status masks in C applications that mix types with and without Zero Copy

This regression was introduced in 6.0.0 and has been fixed in 6.0.1.30, 6.1.2, and 7.1.0. See Crash with NULL listeners and non-none status masks in C applications that mix types with and without Zero Copy in the 6.0.0 Regressions section.

4.3.1.3.7. Arbitrary read access while parsing malicious RTPS message

Arbitrary read access can occur while parsing a malicious RTPS message. User impact with or without Security is a vulnerability in the Connext application that could result in the following:

  • Arbitrary read access while parsing a malicious RTPS message.

  • Remotely exploitable.

  • Potential impact on confidentiality of Connext application.

  • CVSS Base Score: 8.2 HIGH

  • CVSS v3.1 Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Mitigation: protect the network Connext is running so untrusted peers cannot inject malicious RTPS messages.

This vulnerability is fixed in 7.1.0.

[RTI Issue ID CORE-13160]

4.3.1.3.8. DDS fragmentation leads to more fragments than expected for a sample

In 7.0.0, you may notice that when using middleware-level fragmentation and a flow controller where bytes_per_token is set to a value smaller than the minimum transport message_size_max across all installed transports, the number of sample fragments generated for a sample may be bigger than expected. Although this is not a functional issue, it may lead to performance degradation.

This problem is fixed in release 7.1.0.

[RTI Issue ID CORE-13190]

4.3.1.3.9. TCP transport debug library in Windows does not work with IOCP socket monitoring

This regression was introduced in 7.0.0. In release 7.0.0, the debug library for the TCP Transport does not work on Windows® systems when you set the property dds.transport.TCPv4.tcp1.socket_monitoring_kind to WINDOWS_IOCP.

Trying to use the library will result in the following error:

Mx02:c:\jenkins\workspace\connextdds\release7.0.0.0\x64win64vs2017\src\osapi.1.0\srcc\thread\thread.c:2179:RTI0x200003b:!precondition: "strlen(name) >= 16"
RTIOsapiThread_newWithStack:!create initialize

This problem is fixed in release 7.1.0.

[RTI Issue ID COREPLG-654]

4.3.1.3.10. Unexpected warning during discovery when multicast disabled

This regression was introduced in 6.1.1 and has been fixed in 7.1.0. See Unexpected warning during discovery when multicast disabled in the 6.1.1/6.1.2 Regressions section.

4.3.2. Code Generator

4.3.2.1. Fixed in 7.1.0

4.3.2.1.1. Compile-time error when using -constructor with types containing sequence of pointers

This regression was introduced in 6.1.0 and has been fixed in release 7.1.0. See Compile-time error when using -constructor with types containing sequence of pointers in the 6.1.0 Regressions section.

4.3.3. Security Plugins

4.3.3.1. Fixed in 7.2.0

4.3.3.1.1. Discovery time scaled poorly

This regression was introduced in 6.0.0 and has been fixed in 7.2.0. See Discovery time scaled poorly in the 6.0.0 Regressions section.

4.3.3.1.2. Lack of origin authentication led to unnecessary allocation and possible discovery failure

This regression was introduced in 6.1.1 and has been fixed in release 7.2.0. See Lack of origin authentication led to unnecessary allocation and possible discovery failure in the 6.1.1/6.1.2 Regressions section.

4.3.3.2. Fixed in 7.1.0

4.3.3.2.1. Unexpected “Fragment data not supported by this writer” error when using Security

In 7.0.0, you may see the following error when trying to run an application setting the dds.participant.protocol.rtps_overhead property and using the Security Plugins. The same configuration did not fail in previous releases.

ERROR COMMENDFacade_canSampleBeSent:NOT SUPPORTED | Fragment data not supported by this writer.

To work around the issue, you can remove the property dds.participant.protocol.rtps_overhead from the participant configuration. This is also the recommended configuration starting with 7.0.0, since the overhead is automatically calculated by the middleware.

This problem is fixed in release 7.1.0.

[RTI Issue ID SEC-1813]

4.3.3.2.2. Session keys not renewed as often as they should when using RTPS SIGN protection

The Security Plugins update the session keys after protecting some message blocks. The cryptography.max_blocks_per_session property determines how many message blocks can be encrypted using the same session key.

However, cryptography.max_blocks_per_session has an effective value larger than the property value when using RTPS SIGN (or SIGN_WITH_ORIGIN_AUTHENTICATION) protection. The problem leads to slightly overused session keys in some scenarios.

This issue only affects the Security Plugins in 7.0.0 and is fixed in 7.1.0.

[RTI Issue ID SEC-1786]

4.3.3.2.3. Potential crash while decoding protected submessages

This regression was introduced in 6.1.1 and has been fixed in release 7.1.0. See Potential crash while decoding protected submessages in the 6.1.1/6.1.2 Regressions section.

4.3.4. Recording Service

4.3.4.1. Fixed in 7.1.0

4.3.4.1.1. Exception reported when recording or replaying type registered as a union

This regression was introduced in 6.1.0 and has been fixed in release 7.1.0. See Exception reported when recording or replaying type registered as a union in the 6.1.0 Regressions section.

4.3.5. Persistence Service

4.3.5.1. Fixed in 7.1.0

4.3.5.1.1. Persistence Service XSD schema broken

In release 7.0.0, the Persistence Service XSD schema was broken due to an additional closing tag. This affected only the 7.0.0 release. This issue is fixed in release 7.1.0.

[RTI Issue ID PERSISTENCE-276]