5.1. Discovery

5.1.1. [Critical] Port collision on one channel of multichannel DataWriter caused discovery to fail even if another channel had no port collision

Consider the following scenario:

  • You have a DataReader.

  • You have a multichannel DataWriter, which uses specific ports 1234 and 5678.

  • The DataReader discovers the DataWriter, but the matching process for one channel fails due to a port collision that generates this error: assertRemoteWriter:!create entryPort. Another process has already created a socket bound to port 1234.

The DataReader was incorrectly considered unmatched with the DataWriter, even though the other channel did not encounter a port collision.

[RTI Issue ID CORE-15842]

5.1.2. [Critical] Undefined behavior when serializing using any of the builtin discovery plugins

There was undefined behavior when serializing using any of the builtin discovery plugins. This issue could lead to crashes or memory corruption.

[RTI Issue ID CORE-15454]

5.1.3. [Critical] Incorrect locators used on newly created DataWriters or DataReaders after a Locator Reachability event

When creating a DataWriter or DataReader, the locators to be used for communication may be inherited from a local DomainParticipant’s knowledge of the remote DomainParticipant. If a Locator Reachability event occurred before they were created, the DataWriter or DataReader might have attempted to use non-reachable locators.

[RTI Issue ID CORE-15390]

5.1.4. [Critical] DNS Tracking not supported with participants using SPDP2 *

DNS tracking was not supported for DomainParticipants using SPDP2. The DomainParticipant continued sending bootstrap announcements to the IP address of newly resolved hostnames, even if existing participants were using the IP address, resulting in excess traffic.

The DomainParticipant may have also failed to resume sending bootstrap announcements to the IP address that a hostname was resolved to once existing remote participants using that IP address lost liveliness. This caused a failure to discover new remote participants at those IP addresses.

DNS tracking is now supported when using SPDP2.

[RTI Issue ID CORE-14113]

5.1.5. [Major] DomainParticipants failed to announce that endpoint was not reachable when internal clock was monotonic and external clock was real-time

DomainParticipants failed to announce to remote participants that an endpoint was not reachable at a locator when the internal clock was monotonic and the external clock was real-time.

[RTI Issue ID CORE-15366]

5.1.6. [Major] DomainParticipants using SPDP2 and fragmentation of the participant configuration messages failed to complete discovery *

DomainParticipants using SPDP2 and fragmentation of the configuration messages (that is, the participant configuration message was larger than the message_size_max) failed to complete discovery, and the following warning was logged:

WARNING [PARSE MESSAGE|0x0101D6D6,0xC6933A70,0x66CB2656:0x00010187{Entity=DR,MessageKind=DATA_FRAG}|RECEIVE FROM 0x0101D332,0x6CC2F8A4,0x43BA1F0C:0x00010182] COMMENDSrReaderService_onSubmessage:!support fragments. Message dropped.

Now DomainParticipants using SPDP2 can use fragmentation of the configuration messages.

[RTI Issue ID CORE-15257]



* This bug did not affect you if you are upgrading from 6.1.x or earlier.