.. include:: /../getting_started/vars.rst .. _section-Regressions700: Regressions in 7.0.0 ******************** The following regressions occur in *Connext* 7.0.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. .. _CORE-14328: Some properties no longer accept LENGTH_UNLIMITED string as valid value ----------------------------------------------------------------------- This regression was introduced in 7.0.0 and is not yet fixed. Some properties, such as ``dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size``, can't be set to the special "unlimited" value using the string "LENGTH_UNLIMITED". Use "-1" instead. [RTI Issue ID CORE-14328] Fixed in 7.1.0 -------------- 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 :ref:`CORE-12739` in the 6.1.0 Regressions section. 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 :ref:`CORE-12772` in the 6.1.0 Regressions section. Unexpected precondition error with debug libraries on a reliable |DW| 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 :ref:`CORE-13462` in the 6.1.1/6.1.2 Regressions section. 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 :ref:`CORE-12874` in the 6.1.0 Regressions section. 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 :ref:`CORE-12992` in the 6.0.0 Regressions section. 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 :ref:`CORE-13151` in the 6.0.0 Regressions section. 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 has been fixed in 7.1.0. [RTI Issue ID CORE-13160] 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 has been fixed in release 7.1.0. [RTI Issue ID CORE-13190] 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: .. code-block:: text 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 has been fixed in release 7.1.0. [RTI Issue ID COREPLG-654] .. MG-124 Unexpected warning during discovery when multicast disabled ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This regression was introduced in 6.1.1 and has been fixed in 7.1.0. See :ref:`CORE-13403` in the 6.1.1/6.1.2 Regressions section. Code Generator ============== Fixed in 7.1.0 -------------- 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 :ref:`CODEGENII-1596` in the 6.1.0 Regressions section. |RTI_SP_PRODUCT_HEADING| ======================== Fixed in 7.2.0 -------------- Discovery time scaled poorly ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This regression was introduced in 6.0.0 and has been fixed in 7.2.0. See :ref:`section-security-2170` in the 6.0.0 Regressions section. 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 :ref:`SEC-2210` in the 6.1.1/6.1.2 Regressions section. Fixed in 7.1.0 -------------- 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 |RTI_SP_PRODUCT|. The same configuration did not fail in previous releases. .. code-block:: text 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 has been fixed in release 7.1.0. [RTI Issue ID SEC-1813] Session keys not renewed as often as they should when using RTPS SIGN protection ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The |RTI_SP_PRODUCT| 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 |RTI_SP_PRODUCT| in 7.0.0 and has been fixed in 7.1.0. [RTI Issue ID SEC-1786] Potential crash while decoding protected submessages ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This regression was introduced in 6.1.1 and has been fixed in release 7.1.0. See :ref:`SEC-1960` in the 6.1.1/6.1.2 Regressions section. Recording Service ================= Fixed in 7.1.0 -------------- 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 :ref:`RECORD-1339` in the 6.1.0 Regressions section. Persistence Service =================== Fixed in 7.1.0 -------------- Persistence Service XSD schema broken ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ In release 7.0.0, the *Persistence Service* XSD schema is broken due to an additional closing tag. This affects only the 7.0.0 release. This issue has been fixed in release 7.1.0. [RTI Issue ID PERSISTENCE-276] 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.