8.3. Regressions in 7.2.0

The following regressions were introduced in Connext 7.2.0.

8.3.1. Core Libraries

8.3.1.1. Sentinel constant for “invalid” Time contained unexpected value

The sentinel Time value that indicates an “invalid” timestamp is incorrect and doesn’t match the value of an “invalid” SampleInfo::source_timestamp (which can be returned when an instance state is NOT_ALIVE_NO_WRITERS). This makes a comparison such as the following to never be true:

if (info.source_timestamp() == Time::invalid()) {} // never true due to this bug

Starting in 7.3.0, Time::invalid() contains the expected sentinel value.

Fixed in: 7.3.0

[RTI Issue ID CORE-14334]

8.3.1.2. Error message printed for each filtered sample when using writer-side filtering, FlatData, and Zero Copy over shared memory

When using FlatData, Zero Copy over shared memory, and writer-side filtering, every sample that is filtered incorrectly causes an error similar to the following to be logged:

ERROR [0x0101501F,0x044D6680,0xBF657AAB:0x80000002{Entity=DW,Topic=Example CameraImage,Type=CameraImage,Domain=0}|WRITE] REDAThresholdBufferPool_returnBuffer:!attempting to return a buffer to a pool that it was not allocated from.

There is no impact on functionality; the samples are still filtered correctly.

Fixed in: 7.3.0

[RTI Issue ID CORE-14144]

8.3.1.3. RTI Monitor unable to start due to missing nddsjava.jar in rti_connext_dds-7.2.0/lib/java in LM bundles

The nddsjava.jar file is missing in rti_connext_dds-7.2.0/lib/java, making RTI Monitor unable to start. You can work around this issue manually by copying nddsjava.jar from rti_connext_dds-7.2.0/lib/java to rti_connext_dds-7.2.0/resource/app/lib/java. This issue only affects LM bundles and is fixed in 7.3.0. It was also fixed in 7.2.0 shortly after 7.2.0’s initial release.

Fixed in: 7.2.0, 7.3.0

[RTI Issue ID INSTALL-977]

8.3.2. Security Plugins

8.3.2.1. Verbosity of security-related messages is per application

The last DomainParticipant explicitly setting the plugin-specific logging.verbosity property (set by you, in the QoS settings) will apply that setting to all the DomainParticipants within the application and all security-related messages logged from the Connext libraries. This is the behavior in all Connext releases, except for 7.2.0.

Connext 7.2.0 introduced support for running a combination of DomainParticipants from the Builtin Security Plugins library (nddssecurity) and the Lightweight Builtin Security Plugins library (nddslightweightsecurity) inside the same application. In 7.2.0, the logging verbosity (for all security-related messages) of all the DomainParticipants belonging to the same security library is determined by the last DomainParticipant of that library (as opposed to the last DomainParticipant within the application) that your application creates.

Connext 7.3.0 reverts this behavior. In 7.3.0, the logging verbosity for all security-related messages is again determined by the last DomainParticipant that your application creates.

Fixed in: 7.3.0

[RTI Issue ID SEC-2368]

8.3.2.1.1. Memory leak when running Security Plugins SDK tester

Running a Security Plugins tester (AccessControlTester, CryptographyTester, or LightweightTester) causes a memory leak, because the testers don’t finalize the DomainParticipantFactory. This issue has been fixed. Now, the testers call DDS_DomainParticipantFactory_finalize_instance() upon finalization.

Fixed in: 7.3.0

[RTI Issue ID SEC-2279]

8.3.2.1.2. Wrong default Governance configuration for legacy Builtin Secure Logging topic

The Governance configuration for the DDS:Security:LogTopic legacy builtin topic is wrong in Security Plugins 7.2.0 by default. This issue prevents DDS:Security:LogTopic DataReaders from being interoperable with previous versions of Connext and with other vendors. The workaround is to manually configure the topic-level security attributes in the Governance Document:

<topic_rule>
    <topic_expression>DDS:Security:LogTopic</topic_expression>
    <enable_discovery_protection>false</enable_discovery_protection>
    <enable_liveliness_protection>false</enable_liveliness_protection>
    <enable_read_access_control>true</enable_read_access_control>
    <enable_write_access_control>false</enable_write_access_control>
    <metadata_protection_kind>SIGN</metadata_protection_kind>
    <data_protection_kind>ENCRYPT</data_protection_kind>
</topic_rule>

This issue has been fixed. Now, there is no need to configure the builtin logging topic security attributes in the Governance Document. Subscriptions to both the legacy and non-legacy builtin logging topics now work by default.

Fixed in: 7.3.0

[RTI Issue ID SEC-2278]