8.3. Regressions in 7.2.0
The following regressions occurred in Connext 7.2.0, but nearly all were fixed by release 7.3.0 or 7.4.0. If you never installed release 7.2.0, you can ignore this section. See Regressions in 7.3.0.
8.3.1. Core Libraries
8.3.1.1. XCDR serialization of a mutable union with an unknown discriminator value is not compliant with OMG specification
This regression was introduced in 6.0.0 and has not yet been fixed. See XCDR serialization of a mutable union with an unknown discriminator value is not compliant with OMG specification in the 6.0.0 Regressions section.
8.3.1.2. Some properties no longer accept LENGTH_UNLIMITED string as valid value
This regression was introduced in 7.0.0 and is not yet fixed. See Some properties no longer accept LENGTH_UNLIMITED string as valid value in the 7.0.0 Regressions section.
8.3.1.3. Fixed in 7.4.0
8.3.1.3.1. Possible segmentation fault while enabling a DataWriter that enables batching
This regression was introduced in 7.0.0 and has been fixed in 7.4.0. See Possible segmentation fault while enabling a DataWriter that enables batching in the 7.0.0 Regressions section.
8.3.1.3.2. Running out of memory during DomainParticipant creation causes DomainParticipantFactory finalization to hang
This regression was introduced in 7.0.0 and has been fixed in 7.4.0. See Running out of memory during DomainParticipant creation causes DomainParticipantFactory finalization to hang in the 7.0.0 Regressions section.
8.3.1.4. Fixed in 7.3.0
8.3.1.4.1. Potential bus error when calling print and to_string APIs in TypeCode
This regression was introduced in 7.1.0 and is fixed in release 7.3.0. See Potential bus error when calling print and to_string APIs in TypeCode in the 7.1.0 Regressions section.
8.3.1.4.2. Sentinel constant for “invalid” Time contained unexpected value
Due to a regression in 7.2.0, 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.
[RTI Issue ID CORE-14334]
8.3.1.4.4. 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 a 7.2.0 patch release.
[RTI Issue ID INSTALL-977]
8.3.2. Security Plugins
8.3.2.1. Fixed in 7.4.0
8.3.2.1.1. Segmentation fault in Java while enabling a DataWriter that protects payloads and enables batching
This regression was introduced in 7.0.0 and has been fixed in 7.4.0. See Segmentation fault in Java while enabling a DataWriter that protects payloads and enables batching in the 7.0.0 Regressions section.
8.3.2.2. Fixed in 7.3.0
8.3.2.2.2. 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
is fixed in 7.3.0. In 7.3.0, the testers call
DDS_DomainParticipantFactory_finalize_instance()
upon finalization.
[RTI Issue ID SEC-2279]
8.3.2.2.3. 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 is fixed in 7.3.0. In 7.3.0, 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 work by default in 7.3.0.
[RTI Issue ID SEC-2278]
8.3.3. Recording Service
8.3.3.1. Fixed in 7.4.0
8.3.4. Limited Bandwidth Plugins
8.3.4.1. Fixed in 7.3.0
8.3.4.1.1. Limited Bandwidth ZRTPS transport crashes if an external compression library fails to load
This regression was introduced in 6.1.2 and is fixed in release 7.3.0. See Limited Bandwidth ZRTPS transport crashes if an external compression library fails to load in the 6.1.1/6.1.2 Regressions section.