10. Release Notes

• 10.1. Supported Platforms and Programming Languages
• 10.2. What’s New in 2.4.15
  • 10.2.1. Platform-independent code is now separate from OS and network stack integration
  • 10.2.2. Transfer large data samples quickly with Zero Copy v2
• 10.3. What’s Fixed in 2.4.15
  • 10.3.1. [Critical] Failed to deliver samples when prior samples were lost
  • 10.3.2. [Critical] messageLength field was required in RTPS HEADER_EXTENSION for checksum calculations
  • 10.3.3. [Critical] DataReader on a Topic using an appendable type may have received samples with incorrect value
  • 10.3.4. [Critical] Failure to interoperate with other DDS implementations if default multicast locator was specified
  • 10.3.5. [Critical] Connext Cert may have repeated requesting a sample that was no longer available from a DataWriter
  • 10.3.6. [Critical] DataWriter with BEST_EFFORT and TRANSIENT_LOCAL may have run out of resources
  • 10.3.7. [Major] Code generation did not create proper type support for IDL files containing multiple Zero Copy types
  • 10.3.8. [Major] Samples with meta-information were not delivered to the user if they arrived when history cache was full
  • 10.3.9. [Major] Possible segmentation fault when a Zero Copy-enabled DataReader called read() after unmatching with a DataWriter
  • 10.3.10. [Major] Incorrect deserialization of CDR encapsulation padding bits
  • 10.3.11. [Major] Heap memory was allocated by the Zero Copy v2 transport during DDS discovery
  • 10.3.12. [Minor] Incorrect heartbeat sent before first sample when first_write_sequence_number is not 1
  • 10.3.13. [Minor] DDS_String_alloc and related functions failed when passed 0 as length
  • 10.3.14. [Trivial] DDS_Wstring_cmp did not match the implementation name DDS_Wstring_compare
• 10.4. Previous Releases
  • 10.4.1. What’s New in 2.4.12.1
  • 10.4.2. What’s Fixed in 2.4.12.1
• 10.5. Known Issues
  • 10.5.1. Logging mechanism is not included by default
  • 10.5.2. Resources are not freed when calling unregister_instance on a reliable Zero Copy DataWriter
  • 10.5.3. Multiple endpoints not matched properly when using Zero Copy
  • 10.5.4. Cannot set consistency mode for SharedQWriter to anything but ROBUST
  • 10.5.5. VOLATILE Zero Copy DataReaders behave as TRANSIENT_LOCAL
  • 10.5.6. Samples cannot be reclaimed if Zero Copy application does not return loan
  • 10.5.7. Maximum number of components limited to 9
  • 10.5.8. Static endpoint discovery requires unique object IDs across all remote endpoints