4.3. Regressions in 6.1.1/6.1.2

The following regressions occur in Connext 6.1.1/6.1.2.

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 is not yet fixed. 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. Unexpected precondition error with debug libraries on a reliable DataWriter while sending a GAP

In the 6.1.2 and 5.3.1.41 releases, you may see the following precondition error while using the Connext debug libraries.

DL Debug: :         Backtrace:
DL Debug: :    #4      COMMENDSrWriterService_sendGapToRR /rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/commend.1.0/srcC/srw/SrWriterService.c:4096 (discriminator 9) [0x5B101E]
DL Debug: :    #5      COMMENDSrWriterService_onSendDataEvent /rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/commend.1.0/srcC/srw/SrWriterService.c:6570 [0x5BACF6]
DL Debug: :    #6      RTIEventActiveGeneratorThread_loop /rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/event.1.0/srcC/activeGenerator/ActiveGenerator.c:307 [0x28E2FC]
DL Debug: :    #7      RTIOsapiThreadFactory_onSpawned /rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/osapi.1.0/srcC/threadFactory/ThreadFactory.c:208 [0x1F3A42]
DL Debug: :    #8      RTIOsapiThreadFactory_onSpawned /rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/osapi.1.0/srcC/threadFactory/ThreadFactory.c:208 [0x1F3A42]
DL Debug: :    #9      RTIOsapiThreadChild_onSpawned /rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/osapi.1.0/srcC/thread/Thread.c:1941 [0x1EDB64]
DL Debug: :    #10     start_thread /build/glibc-CVJwZb/glibc-2.27/nptl/pthread_create.c:463 [0x76DB]
DL Debug: :    #11     clone /build/glibc-CVJwZb/glibc-2.27/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:97 [0x12161F]
DL Fatal: : FATAL rCoRTInk####Evt [0x01014F91,0x39810444,0x4EC68AEA:0x000004C2|RECEIVE FROM remote DR (GUID: 0x01015FBD,0x5892DC7E,0x9DB082D4:0x000004C7).
] Mx00:/rti/jenkins/workspace/connextdds_ci_fastbuild-debug_develop/commend.1.0/srcC/srw/SrWriterService.c:4099:RTI0x200003b:!precondition: "((((gapStartSn)->high) > (((&(gapBitmap)->_lead))->high)) ? 1 : ((((gapStartSn)->high) < (((&(gapBitmap)->_lead))->high)) ? -1 : ((((gapStartSn)->low) > (((&(gapBitmap)->_lead))->low)) ? 1 : ((((gapStartSn)->low) < (((&(gapBitmap)->_lead))->low)) ? -1 : 0)))) >= 0"
DL Error: : ERROR [0x01014F91,0x39810444,0x4EC68AEA:0x000004C2|RECEIVE FROM remote DR (GUID: 0x01015FBD,0x5892DC7E,0x9DB082D4:0x000004C7).
] COMMENDSrWriterService_onSendDataEvent:!send GAP

This error is generated by a reliable DataWriter sending a GAP to a reliable DataReader. After the error is printed, the DataReader may stop receiving data from the DataWriter, leading to a non-recoverable situation. This problem does not occur with release libraries. This problem is fixed in 6.1.2.3 and 7.1.0 releases.

[RTI Issue ID CORE-13462]

4.3.1.3.2. Unexpected warning during discovery when multicast disabled

Connext logs a warning during the discovery process when multicast is disabled. The message warns about unreachable multicast locators. The message is unexpected and has been removed in release 7.1.0.

[RTI Issue ID CORE-13403]

4.3.1.4. Fixed in 7.1.0 and 6.1.2

4.3.1.4.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.4.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.4.3. 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.4.4. 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.4.5. 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 Section 4.6.1.1.2 in the 6.0.0 Regressions section.

4.3.1.5. Fixed in 7.0.0 and 6.1.2

4.3.1.5.1. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator

This regression was introduced in 6.0.0 and has been fixed in releases 7.0.0 and 6.1.2. See Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator in the 6.0.0 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.1.0

4.3.3.1.1. Potential crash while decoding protected submessages

Release 6.1.1 introduced several performance optimizations to Submessage Protection decoding. There is an issue with one of these optimizations, potentially resulting in a rare crash on the receiver (DataWriter or DataReader) while decoding a protected submessage. In particular, this issue is triggerable if any of the following is true for at least one DataWriter/DataReader pair:

metadata_protection_kind is set to a value different from NONE
discovery_protection_kind is set to a value different from NONE and enable_discovery_protection is set to TRUE
liveliness_protection_kind is set to a value different from NONE and enable_liveliness_protection isset to TRUE

This issue, which is more likely to trigger when the sender’s DomainParticipant is deleting all of its endpoints, has been fixed in release 7.1.0. In release 7.1.0, decoding protected submessages no longer results in a crash.

[RTI Issue ID SEC-1960]

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.