10.3. What’s Fixed in 2.4.16

The following are fixes since Connext Cert 2.4.15.

[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.

• 10.3.1. Discovery
  • 10.3.1.1. [Critical] Lost INFO_DST messages with GUIDPREFIX_UNKNOWN
  • 10.3.1.2. [Major] DomainParticipants continued to send DATA(p) messages to nonexistent remote participants
• 10.3.2. Reliability Protocol and Wire Representation
  • 10.3.2.1. [Major] A reliable DataReader may have stopped receiving data
• 10.3.3. Generated Code (C)
  • 10.3.3.1. [Major] Code Generator generated examples using IP addresses without transport prefix
• 10.3.4. APIs (C)
  • 10.3.4.1. [Major] DDS_Publisher_lookup_datawriter returned a DataWriter created by a different Publisher
  • 10.3.4.2. [Major] DDS_Subscriber_lookup_datareader returned a DataReader created by a different Subscriber
  • 10.3.4.3. [Minor] Incorrect error code for DDS_DomainParticipantQos_initialize and DDS_DomainParticipantQos_copy
• 10.3.5. Memory Leaks/Growth
  • 10.3.5.1. [Major] Resources were not freed when calling unregister_instance on a reliable Zero Copy DataWriter
• 10.3.6. Data Corruption
  • 10.3.6.1. [Critical] Historical samples overwritten in the DataWriter queue when using TRANSIENT_LOCAL over UDPv4
• 10.3.7. Interoperability
  • 10.3.7.1. [Major] Zero Copy communication failed when applications were started from different directories
  • 10.3.7.2. [Minor] OSAPI_SharedMemorySegment_get_max_size() functioned incorrectly on QNX systems
• 10.3.8. Other
  • 10.3.8.1. [Major] Possible race condition with Zero Copy shared memory API
  • 10.3.8.2. [Major] DataWriter with finite timestamp failed to send data if date exceeded January 2038
  • 10.3.8.3. [Major] Connext Cert would not work if year exceeded 2038
  • 10.3.8.4. [Minor] Multiple endpoints did not match properly when using Zero Copy transfer
  • 10.3.8.5. [Minor] SYSTEM_RESOURCE_LIMITS.max_components QoS setting documented incorrectly
  • 10.3.8.6. [Trivial] DDS_Wstring_cmp did not match the implementation name DDS_Wstring_compare