10.3. What’s Fixed in 4.1.0

The following are fixes since Connext Micro 4.0.1.

[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. [Major] Participants did not perform discovery correctly when on_data_on_readers callback was set
  • 10.3.1.2. [Minor] Incorrect data fragmentation of discovery messages for DomainParticipant built-in topic
• 10.3.2. Usability
  • 10.3.2.1. [Minor] MAG failed to generate warnings for certain unsupported QoS
• 10.3.3. Transports
  • 10.3.3.1. [Major] Multicast sockets always bound to the multicast address on non-Windows platforms
• 10.3.4. Reliability Protocol and Wire Representation
  • 10.3.4.1. [Critical] Failed to deliver samples when prior samples were lost
  • 10.3.4.2. [Major] Delayed or failed to deliver large samples on unreliable networks
  • 10.3.4.3. [Minor] Piggyback heartbeats were not included when using asynchronous publication
• 10.3.5. APIs (C or Traditional C++)
  • 10.3.5.1. [Major] DDS_DomainParticipantFactory_delete_participant was not thread-safe
  • 10.3.5.2. [Minor] C++ constructor did not allocate memory for Topic and Type names
  • 10.3.5.3. [Trivial] C++ API Reference contained incorrect <<cert>> references
  • 10.3.5.4. [Trivial] Non-descriptive API failure messages
• 10.3.6. XML Configuration
  • 10.3.6.1. [Minor] Invalid code when using a flow controller
• 10.3.7. Crashes
  • 10.3.7.1. [Critical] Segmentation fault occurred when an asynchronous publisher tried to send a missing data fragment
  • 10.3.7.2. [Critical] Segmentation fault occurred when creating or finalizing a DataWriter or DataReader while using asynchronous publication
  • 10.3.7.3. [Critical] Potential race condition and crash occurred when a DataWriter waited for resources
  • 10.3.7.4. [Critical] Potential race condition and crash occurred when a DataWriter unmatched with a remote entity
  • 10.3.7.5. [Minor] Integer overflow when setting MTU lower than 448 bytes
• 10.3.8. Hangs
  • 10.3.8.1. [Critical] Ungracefully terminated QNX processes using SHMEM transport prevented startup of new processes due to unclosed POSIX semaphores
• 10.3.9. Memory Leaks/Growth
  • 10.3.9.1. [Minor] Failed to cleanup resources when DomainParticipant creation failed
• 10.3.10. Data Corruption
  • 10.3.10.1. [Critical] Potential data corruption from race condition when using KEEP_LAST and publishing asynchronously
• 10.3.11. Interoperability
  • 10.3.11.1. [Critical] Incorrect handling of RTPS messages with submessages from different participants
• 10.3.12. Other
  • 10.3.12.1. [Critical] Lost samples or fragments not repaired when using a flow controller
  • 10.3.12.2. [Major] Enabling asynchronous publication on DataWriter caused RTPS messages to fail
  • 10.3.12.3. [Major] Finalizing a participant might have failed when using DPSE
  • 10.3.12.4. [Major] Samples with meta-information were not delivered to the user if they arrived when history cache was full
  • 10.3.12.5. [Minor] Flow controllers incorrectly delayed sending packets
  • 10.3.12.6. [Minor] DataWriters with KEEP_ALL History may not have sent all historical samples
  • 10.3.12.7. [Trivial] Illegal reflective access warning when running MAG with OpenJDK™ 11
  • 10.3.12.8. [Trivial] Incorrect example instructions in the User’s Manual
  • 10.3.12.9. [Trivial] Micro transformation example failed to compile