5.11. Logging

5.11.1. [Major] Misleading warning message when one non-loopback interface doesn’t support multicast *

If the network interfaces on a machine included an interface that supports multicast and a non-loopback interface that does not support multicast, and you sent a multicast packet from the machine, then a warning message like this one would incorrectly appear:

NDDS_Transport_UDP_send:FAILED TO SEND | Message with 64 bytes over 2 interface(s). Total bytes sent: 64. Total bytes to send: 128.

In this example, the multicast packet is 64 bytes, and Connext was incorrectly trying to send it over two interfaces instead of one (hence, the 128). This problem, which only affected versions 7.3.0 and above, has been fixed by only trying to send the packet over the interface that supports multicast.

[RTI Issue ID CORE-15833]

5.11.2. [Major] Unexpected warning during DomainParticipant enablement when locator reachability enabled *

If you set the DomainParticipantQos::discovery_config::locator_reachability_lease_duration to a value other than DDS_DURATION_INFINITE, then Connext logged this warning during DomainParticipant enablement:

COMMENDAnonWriterService_assertRemoteReader:The remote reader with GUID 0x00000000,0x00000000,0x00000000:0x00020187 has no addressable locators.

This harmless warning was introduced in 7.0.0 and has now been removed.

[RTI Issue ID CORE-15718]

5.11.3. [Trivial] Incorrect warning printed for best-effort synchronous DataWriters that required DDS fragmentation *

RTI Connext incorrectly printed a warning like the following for best-effort DataWriters when the samples’ serialized size was larger than the configured message_size_max, the data type was not unbounded, and asynchronous publish mode was not enabled:

WARNING [...] PRESPsService_enableLocalWriterWithCursor:Max serialized size of type 'YourType' (N) exceeds the transport's message size max (N). Consider using asynchronous publishing or increasing message size max otherwise samples with a serialized size larger than N will not be able to be sent.

Asynchronous publishing is only a requirement for DDS fragmentation if the ReliabilityQosPolicy of your DataWriter is set to reliable.

RTI Connext no longer prints the warning for best-effort DataWriters.

[RTI Issue ID CORE-14968]

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