6.4.4. Fixes Related to Transports
6.4.4.1. [Critical] Possible data loss after a Connext application lost its multicast interfaces or gained its first multicast interface
The IP mobility feature detects when the interfaces of an application change, then propagates these changes. If an IP mobility event causes either the loss of the last interface that supported multicast or the gain of the first interface that supports multicast, the way other applications communicate with the application that experienced the IP mobility event changes.
Previously, that transition did not happen properly and may have led to data losses. This problem has been fixed. Now, communication is not affected by these interface changes.
[RTI Issue ID CORE-12609]
6.4.4.2. [Major] DomainParticipant with non-default metatraffic_transport_priority QoS did not complete discovery
A DomainParticipant that had a non-default metatraffic_transport_priority in the DISCOVERY QoS Policy was not able to complete endpoint discovery due to a unicast metatraffic channel that was not created correctly. (The channel is used by the participant to send Data(R) and Data(W).)
This issue was introduced in 6.1.0. This issue has been resolved.
[RTI Issue ID CORE-12739]
6.4.4.3. [Major] TCP Transport did not run with Windows debug libraries when socket_monitoring_kind was set to IOCP *
An internal error prevented the TCP transport from running on Windows with debug libraries when the socket_monitoring_kind was set to the recommended value of NDDS_TRANSPORT_TCPV4_SOCKET_MONITORING_KIND_WINDOWS_IOCP. The error has been corrected.
[RTI Issue ID COREPLG-654]
6.4.4.4. [Minor] dds.transport.minimum_compatibility_version property did not properly adjust locator format
Connext 5.3.0 introduced a new shared memory locator format. DomainParticipants in Connext 5.3.0 (and above) use the new locator format by default. To allow interoperability with Connext versions before 5.3.0, you must indicate to DomainParticipants to use the old locator format.
There are two properties for telling a DomainParticipant to use the old locator format: dds.transport.use_530_shmem_locator_matching (undocumented and deprecated) and dds.transport.minimum_compatibility_version. The latter is a newer property that combines several other properties. Its purpose is to set the transport to be compatible with the specified version in a simplified manner.
The problem with the newer property, dds.transport.minimum_compatibility_version, was that it did not adjust the locator format depending on the Connext version. The workaround was to use the dds.transport.use_530_shmem_locator_matching property instead. This issue has been fixed. You can now use dds.transport.minimum_compatibility_version without issue.
[RTI Issue ID CORE-12789]
* This bug does not affect you if you are upgrading from 6.1.x or earlier.