5.2. What’s Fixed in 7.6.0

This section describes bugs fixed in Connext 7.6.0. These are fixes since 7.5.0, described in Previous Releases.

Connext 7.6.0 is an early access release. See the Connext Versions and Lifecycle page for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

[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.

• 5.2.1. Discovery
  • 5.2.1.1. [Critical] Port collision on one channel of multichannel DataWriter caused discovery to fail even if another channel had no port collision
• 5.2.2. Serialization and Deserialization
  • 5.2.2.1. [Critical] Unexpected error messages when disposing of an instance while using batching and setting serialize_key_with_dispose to TRUE
• 5.2.3. Usability
  • 5.2.3.1. [Critical] Locator Reachability DataReader could not receive assertions from more than four DomainParticipants
  • 5.2.3.2. [Minor] DDS_RTPS_AUTO_ID_FROM_MAC failed if MAC address had all zeros for first 4 bytes or last 4 bytes
  • 5.2.3.3. [Minor] Inconsistent QoS error when enabling Monitoring Library 2.0 with a default profile (is_default_qos = TRUE)
• 5.2.4. Transports
  • 5.2.4.1. [Major] TCP Transport did not properly enforce system FD_SETSIZE hard limits for select() socket monitoring
  • 5.2.4.2. [Minor] Possible failure to create DomainParticipant if using multicast
• 5.2.5. Reliability Protocol and Wire Representation
  • 5.2.5.1. [Critical] Unexpected data loss when using batching and finite reader resource limits
• 5.2.6. Performance and Scalability
  • 5.2.6.1. [Critical] Slower DDS Entity creation in large applications
• 5.2.7. Debuggability
  • 5.2.7.1. [Major] Duplicate network traffic captures when creating WaitSets, AsyncWaitSets, or GuardConditions
• 5.2.8. Content Filters and Query Conditions
  • 5.2.8.1. [Critical] Unexpected data loss when using writer-side content filtering and changing QoS
  • 5.2.8.2. [Critical] Historical sample loss for late-joining DataReaders setting protocol.virtual_guid
• 5.2.9. TopicQueries
  • 5.2.9.1. [Major] max_samples_per_remote_writer resource limit not honored in some cases when using an unkeyed Topic and TopicQueries
• 5.2.10. Logging
  • 5.2.10.1. [Major] Unexpected warning during DomainParticipant enablement when locator reachability enabled
  • 5.2.10.2. [Major] Misleading warning message when one non-loopback interface doesn’t support multicast
  • 5.2.10.3. [Trivial] Isolated RTIOsapiUtility_strcat error on DomainParticipant creation
• 5.2.11. Dynamic Data
  • 5.2.11.1. [Minor] Unable to set negative values for int8 union discriminators when using Dynamic Data
• 5.2.12. APIs (C or Traditional C++)
  • 5.2.12.1. [Minor] Traditional C++ DDS_KeyedString and DDS_KeyedOctets constructors allowed 0 for a string size
• 5.2.13. APIs (Java)
  • 5.2.13.1. [Critical] Java keyhash calculation error with mutable types in XCDR
• 5.2.14. APIs (Python)
  • 5.2.14.1. [Major] Enhanced logging support in RTI Connext Python API with output_handler_extended
• 5.2.15. APIs (Multiple Languages)
  • 5.2.15.1. [Major] The result of cdr_serialized_sample_max_size was too small if the maximum size was greater than 4 GB
  • 5.2.15.2. [Major] Non-Java register_type failed if the maximum size was greater than 2 GB
  • 5.2.15.3. [Minor] Enum label not printed when there was only one enum member
  • 5.2.15.4. [Minor] Inconsistent QoS error when setting builtin discovery channels
• 5.2.16. XML Configuration
  • 5.2.16.1. [Trivial] Unexpected messages printed in console when there was an error parsing XML application configuration file
  • 5.2.16.2. [Major] Union types loaded from XML did not set ID values correctly when using autoid=”hash”
  • 5.2.16.3. [Major] XML namespace parsing error in QoS profiles
• 5.2.17. Entities
  • 5.2.17.1. [Major] Unable to create DistLogger singleton if remote administration was disabled
• 5.2.18. Crashes
  • 5.2.18.1. [Critical] Potential stack overflow in Connext applications when parsing XML files with a custom DTD with deeply nested entity references
  • 5.2.18.2. [Critical] Possible crash when accessing information about a remote endpoint at the same time that the endpoint was being removed
  • 5.2.18.3. [Major] Changes in RTI Connext logging behavior for Windows desktop applications
  • 5.2.18.4. [Critical] Modern C++ Distributed Logger may have crashed upon instance finalization
  • 5.2.18.5. [Critical] Segmentation fault when using Network Capture APIs concurrently with DomainParticipantFactory deletion
  • 5.2.18.6. [Critical] Potential crash while printing the log message after an error
  • 5.2.18.7. [Critical] Segmentation fault when a DomainParticipant failed to be created
  • 5.2.18.8. [Critical] Segmentation fault and precondition errors with Monitoring Library 2.0 when Entities were deleted
  • 5.2.18.9. [Critical] Possible crash when metric value changed when Monitoring Library 2.0 was being disabled
• 5.2.19. Hangs
  • 5.2.19.1. [Critical] Calling ignore_participant during a ParticipantBuiltinTopicDataDataReader on_data_available callback triggered by the deletion of a remote DomainParticipant led to a hang or unexpected error message
  • 5.2.19.2. [Critical] Potential deadlock when calling DDS_DomainParticipantFactory_set_qos and DDS_DomainParticipantFactory_finalize_instance
  • 5.2.19.3. [Critical] Potential deadlock when using Network Capture utility APIs concurrently with DDS calls
  • 5.2.19.4. [Critical] Hang of QNX application using shared memory if one of the shared semaphores was in an unusable state
  • 5.2.19.5. [Major] Calling ignore_participant when using the on_data_available callback to process a ParticipantBuiltinTopicData with partial_configuration led to a hang during DomainParticipant deletion
• 5.2.20. Memory Leaks/Growth
  • 5.2.20.1. [Critical] Spike in memory usage when creating a DataWriter using Durable Writer History to restore samples
  • 5.2.20.2. [Major] RTI DDS Spy showed DDS_DataReader_get_matched_publication_participant_data error before leaking memory
  • 5.2.20.3. [Major] DomainParticipantFactory finalization failed even if all the DomainParticipants were deleted
  • 5.2.20.4. [Minor] Memory leak upon Transport TCP creation failure because of invalid configuration
• 5.2.21. Data Corruption
  • 5.2.21.1. [Critical] Serialization errors in Windows when publishing remote debugging telemetry with Monitoring Library 2.0
• 5.2.22. OMG Specification Compliance
  • 5.2.22.1. [Major] Incorrect value of an infinite duration in non-Java APIs
  • 5.2.22.2. [Minor] Consistency between max_samples_per_instance and max_samples was not enforced for unkeyed topics
• 5.2.23. Vulnerabilities
  • 5.2.23.1. [Critical] Potential heap buffer read overflow in Connext applications when using a malicious license string
  • 5.2.23.2. [Critical] Potential invalid read memory access in Connext applications when subscribing to PublicationBuiltinTopicData
  • 5.2.23.3. [Critical] Potential invalid read memory access in Connext applications during endpoint discovery
• 5.2.24. Other
  • 5.2.24.1. [Critical] Possible Connext validation error while using a valid license
  • 5.2.24.2. [Critical] Data races on architectures with weak memory models
  • 5.2.24.3. [Major] DomainParticipantFactoryQos could not be retrieved from QosProvider
  • 5.2.24.4. [Major] Incorrect hexadecimal formatting for uint8 and octet
  • 5.2.24.5. [Major] Printing to XML missed quotes for external union members
  • 5.2.24.6. [Major] Printing an IDL or XML enum with a default literal produced incorrect output
  • 5.2.24.7. [Major] Printing an enum default literal printed the ordinal value instead of enumerator name
  • 5.2.24.8. [Major] XML parser rejected external members with ranges excluding zero
  • 5.2.24.9. [Major] Incorrect string representation of union DynamicType with arrays of sequences
  • 5.2.24.10. [Major] Error parsing an XML with an external typedef
  • 5.2.24.11. [Major] Invalid escaping of special characters in default strings for XML and IDL output
  • 5.2.24.12. [Major] DynamicType with default string value incorrectly formatted for XML format
  • 5.2.24.13. [Minor] Multiple attachments of same Condition to a WaitSet
  • 5.2.24.14. [Major] Error when parsing an XML with a struct that has an enum member with a default enumerator
  • 5.2.24.15. [Major] XML string literal interpretation divergence between Core Libraries and Code Generator
  • 5.2.24.16. [Major] XML parser did not parse scientific notation when exponent included an explicit positive sign
  • 5.2.24.17. [Major] Error when parsing an XML with a union that has a member with a default value
  • 5.2.24.18. [Minor] Building a Connext application with Wundef warning category could generate unexpected warnings