8.3.1. Discovery¶
8.3.1.1. [Critical] Lost INFO_DST messages with GUIDPREFIX_UNKNOWN¶
Connext Micro may have silently discarded RTPS INFO_DST messages
containing a guidPrefix of 0x0 (GUIDPREFIX_UNKNOWN).
[RTI Issue ID MICRO-8751]
8.3.1.2. [Critical] Failure to interoperate with other DDS implementations if default multicast locator was specified¶
Connext Micro did not interoperate with other DDS implementations when the default multicast locator was specified.
[RTI Issue ID MICRO-5148]
8.3.1.3. [Major] Possible mismatched endpoint messages during discovery¶
If a DomainParticipant received an endpoint discovery message and lacked
sufficient resources to store the endpoint, Connext Micro would still acknowledge the
message, potentially leading to a mismatch in discovery states between
DomainParticipants. Now, if a DomainParticipant cannot store an endpoint
discovery message due to insufficient resources (and
DomainParticipantQos.discovery.enable_endpoint_discovery_queue is set to
DDS_BOOLEAN_TRUE), the message is queued for later processing when
resources become available.
[RTI Issue ID MICRO-10044]
8.3.1.4. [Major] DomainParticipants continued to send DATA(p) messages to nonexistent remote participants¶
A DomainParticipant might have continued to send DATA(p) discovery messages to remote DomainParticipants that were once discovered but no longer exist.
[RTI Issue ID MICRO-8747]
8.3.1.5. [Minor] Participants using DPDE sent one extra announcement message¶
DomainParticipants using DPDE sent one more participant announcement message than expected for discovery purposes.
[RTI Issue ID MICRO-8257]