.. include:: /../getting_started/vars.rst .. _section-Regressions720: Regressions in 7.2.0 ******************** The following regressions occur in *Connext* 7.2.0. Core Libraries ============== 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 :ref:`CORE-12240` in the 6.0.1 Regressions section. Durable Writer History properties cannot be set on DomainParticipant -------------------------------------------------------------------- This regression was introduced in 6.0.1 and is not yet fixed. See :ref:`CORE-13516` in the 6.0.1 Regressions section. 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 :ref:`CORE-14328` in the 7.0.0 Regressions section. Fixed in 7.3.0 -------------- Potential bus error when calling print and to_string APIs in TypeCode ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This regression was introduced in 7.1.0 and will be fixed in release 7.3.0. See :ref:`CORE-13968` in the 7.1.0 Regressions section. 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()`` will contain the expected sentinel value. [RTI Issue ID CORE-14334] 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 functionally, the samples are still filtered correctly. This issue will be fixed in 7.3.0. [RTI Issue ID CORE-14144] 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 will be fixed in 7.3.0. It was also fixed in a 7.2.0 patch release. [RTI Issue ID INSTALL-977] |RTI_SP_PRODUCT_HEADING| ======================== Fixed in 7.3.0 -------------- Verbosity of security-related messages is per application ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The last |DP| explicitly setting the plugin-specific ``logging.verbosity`` property (set by you, in the QoS settings) will apply that setting to all the |DPs| 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 |DPs| from the |SP_BUILTIN| library (``nddssecurity``) and the |LIGHT_SP_BUILTIN| library (``nddslightweightsecurity``) inside the same application. In 7.2.0, the logging verbosity (for all security-related messages) of all the |DPs| belonging to the same security library is determined by the last |DP| of that library (as opposed to the last |DP| within the application) that your application creates. |CONNEXT| 7.3.0 will revert this behavior. In 7.3.0, the logging verbosity for all security-related messages will again be determined by the last |DP| that your application creates. [RTI Issue ID SEC-2368] 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 will be fixed in 7.3.0. In 7.3.0, the testers will call ``DDS_DomainParticipantFactory_finalize_instance()`` upon finalization. [RTI Issue ID SEC-2279] 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: :: DDS:Security:LogTopic false false true false SIGN ENCRYPT This issue will be fixed in 7.3.0. In 7.3.0, there will be 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 should work by default in 7.3.0. [RTI Issue ID SEC-2278] Limited Bandwidth Plugins ========================= Fixed in 7.3.0 -------------- Limited Bandwidth ZRTPS transport crashes if an external compression library fails to load ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This regression was introduced in 6.1.2 and will be fixed in release 7.3.0. See :ref:`COREPLG-719` in the 6.1.1/6.1.2 Regressions section.