4. What’s Fixed in 7.7.0

This section describes bugs fixed in Connext 7.7.0. These are fixes since 7.6.0.

Connext 7.7.0 is the first production release in the 7.7 long-term support (LTS) series. It is built upon and combines all of the fixes in releases 7.4.0, 7.5.0, and 7.6.0. 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.

• 4.1. Serialization and Deserialization
  • 4.1.1. [Critical] Endpoint serialization/deserialization failure after deleting DomainParticipants if setting different xTypes compliance masks with NDDS_Config_set_xtypes_compliance_mask
• 4.2. Usability
  • 4.2.1. [Minor] Lack of allowed multicast interfaces did not cause Connext to ignore multicast addresses
  • 4.2.2. [Minor] Error when configuring AllocationSettings with initial equals to maximum
  • 4.2.3. [Minor] Monitoring Library 2.0 required a license when used in DDS Ping or DDS Spy with license-managed bundles
• 4.3. Transports
  • 4.3.1. [Critical] Applications using Real-Time WAN may have stopped communicating after IP mobility events
  • 4.3.2. [Major] IP mobility functionality did not detect when network interfaces gained multicast capability
  • 4.3.3. [Minor] Zero-Copy DataReaders did not filter out redundant samples
  • 4.3.4. [Minor] Incorrect information in shared memory log message when out of resources
  • 4.3.5. [Minor] DomainParticipant failed to be enabled if a network interface with UDPv4 address 0.0.0.0 was detected
• 4.4. Reliability Protocol and Wire Representation
  • 4.4.1. [Critical] Sample may not have been delivered to a DataReader in a Required Subscription
  • 4.4.2. [Critical] Samples lost if new DataReader created on same topic and DomainParticipant as existing DataReaders using async publishing
  • 4.4.3. [Critical] Sample may not have been delivered to a DataReader using application-level acknowledgments
  • 4.4.4. [Major] Unexpected precondition error sending repair to DataReaders with 16 locators
• 4.5. Performance and Scalability
  • 4.5.1. [Critical] Performance degradation with durable writer history
  • 4.5.2. [Critical] Performance degradation with Durable Writer History in write-intensive scenarios
  • 4.5.3. [Major] Inefficient repair of fragmented samples caused performance degradation during large data transmission
• 4.6. Debuggability
  • 4.6.1. [Minor] polling_period was not required to be a positive value
  • 4.6.2. [Minor] take_discovery_snapshot may have provided inaccurate information for remote endpoints
  • 4.6.3. [Minor] Incorrect timestamp in log messages with microseconds higher than 500000
  • 4.6.4. [Trivial] Backtraces did not correctly print addresses higher than 0xFFFFFFFF
• 4.7. TopicQueries
  • 4.7.1. [Major] Inefficient O(n^2) reader-side performance when creating multiple TopicQueries simultaneously
• 4.8. Logging
  • 4.8.1. [Trivial] Improved log messages for inconsistent WireProtocolQosPolicy values
  • 4.8.2. [Trivial] Confusing log message when DataWriter could not queue items *
• 4.9. APIs (C or Traditional C++)
  • 4.9.1. [Minor] DDS_DataWriter_is_sample_app_acknowledged didn’t check for NULL for is_app_ack parameter
• 4.10. APIs (Modern C++ API)
  • 4.10.1. [Critical] Implicit destruction of Modern C++ entities inside their Listeners
  • 4.10.2. [Major] Excessive memory allocation in rti::core::xtypes::convert function
  • 4.10.3. [Major] find_datawriters/readers APIs didn’t work with XML-Based Application Creation
  • 4.10.4. [Minor] Incorrect implementation of BuiltinTopicReaderResourceLimits default constructor
  • 4.10.5. [Minor] Missing Modern C++ Distributed Logger import library on Windows
• 4.11. APIs (Java)
  • 4.11.1. [Major] Some BuiltinTopicKey_t’s functions did not work properly
• 4.12. APIs (C# API)
  • 4.12.1. [Major] .NET API built with only .NET Standard 2.0 as target framework
  • 4.12.2. [Minor] DomainParticipant creation may not have respected EntityFactory auto-enable policy in C# API
• 4.13. APIs (Python)
  • 4.13.1. [Trivial] Python API: mypy failures on Windows due to non-ASCII character in docstrings
• 4.14. Dynamic Data
  • 4.14.1. [Minor] Unbounded Sequences incorrectly converted to string from DynamicType
• 4.15. XML Configuration
  • 4.15.1. [Minor] Setting monitoring.telemetry_data.metrics in a derived profile or using an XML snippet did not override inherited values
• 4.16. Entities
  • 4.16.1. [Critical] TransportMulticast QoS locators not properly tracked by locator reachability *
  • 4.16.2. [Minor] Misleading log messages when printing or converting to string non-default TransportMulticast QoS policy
• 4.17. Crashes
  • 4.17.1. [Critical] Possible crash if configuration of Monitoring Library 2.0 was remotely modified while an entity was being destroyed
  • 4.17.2. [Critical] Crash when dividing by zero in XML type definition
  • 4.17.3. [Critical] DataWriter using Durable Writer History and not using Required Subscription crashed when communicating with a DataReader with a role_name
  • 4.17.4. [Critical] Possible crash when deleting an Entity while Monitoring Library 2.0 was enabled
  • 4.17.5. [Critical] Crash when concurrently modifying QoS profiles with Monitoring QoS policy set in default factory profile
  • 4.17.6. [Critical] Crash when using DDS_RECOVER_INSTANCE_STATE_CONSISTENCY and multiple writers updating the same instances
  • 4.17.7. [Critical] Segmentation fault in DataReader that was created disabled when using instance state consistency
  • 4.17.8. [Major] Precondition added to rti::flat::StringBuilder::set_string() and rti::flat::PrimitiveSequenceBuilder<T>::add_n()
• 4.18. Hangs
  • 4.18.1. [Critical] Possible hang in TCP transport when failing to send a message
• 4.19. Memory Leaks/Growth
  • 4.19.1. [Critical] Memory use by Monitoring Library 2.0 may have grown unbounded over time
  • 4.19.2. [Critical] Unbounded memory growth when setting receive_window_size on DataReader
  • 4.19.3. [Critical] Memory leak in DataWriter when matching reliable DataReader
  • 4.19.4. [Critical] History depth not honored after instance transitioned from NOT_ALIVE to ALIVE state
  • 4.19.5. [Major] Memory leak when UDP receive socket creation failed
  • 4.19.6. [Major] Memory leak in Monitoring Library 2.0 when mixing library types
  • 4.19.7. [Minor] Unbounded memory growth in Modern C++ when creating and deleting DynamicData topics of the same type
  • 4.19.8. [Minor] Memory leak when disabling Monitoring Library 2.0 in Traditional C++
• 4.20. Data Corruption
  • 4.20.1. [Critical] Data corruption in Monitoring Library 2.0 due to race condition during event and log processing
  • 4.20.2. [Major] Monitoring Library 2.0 failed to create dependent Entities when type_object_max_serialized_length and type_code_max_serialized_length were 0 *
  • 4.20.3. [Minor] Converting a GUID_t to a BuitinTopicKey_t had issues when high bit was set
• 4.21. OMG Specification Compliance
  • 4.21.1. [Major] Samples of mutable types may have been dropped when bit FLAG_MUST_UNDERSTAND was set on key members
• 4.22. Interoperability
  • 4.22.1. [Major] RTPS Header Extension timestamp used incorrect clock
  • 4.22.2. [Major] TypeConsistencyEnforcement::ignore_member_names did not work in some cases
• 4.23. Vulnerabilities
  • 4.23.1. [Critical] Potential unauthorized access to instance information in Connext applications
  • 4.23.2. [Critical] Potential Denial of Service in Connext applications when parsing XML files
  • 4.23.3. [Critical] Potential heap buffer write overflow and memory leak in Connext applications when parsing an XML type
  • 4.23.4. [Critical] Potential heap buffer read overflow in Connext applications when parsing an XML type
  • 4.23.5. [Critical] Potential out-of-bounds write in Connext when using Durable Writer History
  • 4.23.6. [Critical] Potential external entity attack (XXE) in Connext applications when parsing malicious XML files
  • 4.23.7. [Critical] Potential heap-based buffer overflow when parsing malicious XML configuration files
  • 4.23.8. [Critical] Potential out-of-bounds read in Core Libraries on invalid XML constant expression
• 4.24. Other
  • 4.24.1. [Critical] AppAck messages exceeded underlying transport message size
  • 4.24.2. [Trivial] Incorrect partition labels in DDS Spy