Release Notes

• 1. System Requirements
  • 1.1. Supported Platforms
    • 1.1.1. RTI Architecture Names
    • 1.1.2. APIs
    • 1.1.3. Transports
    • 1.1.4. Infrastructure Services
    • 1.1.5. Other Connext Professional Libraries
    • 1.1.6. Core Library Features
    • 1.1.7. Tools
    • 1.1.8. Connext Security Extensions and Other Add-ons
    • 1.1.9. Footnotes
  • 1.2. Requirements when Using Microsoft Visual Studio
  • 1.3. Disk and Memory Usage
• 2. Compatibility
  • 2.1. Wire Protocol Compatibility
  • 2.2. Code and Configuration Compatibility
  • 2.3. Extensible Types Compatibility
• 3. What’s New in 7.5.0
  • 3.1. Python RPC API now fully productized and supported
  • 3.2. More efficient endpoint discovery for RPC and Request-Reply
  • 3.3. Improved DataWriter queue sample memory management eliminates required configuration for unbounded types
  • 3.4. Enhanced out-of-the-box network performance with updated socket buffer sizes
  • 3.5. Improved scalability for applications using writer-side content filtering
  • 3.6. Initial discovery performance improvements in large systems with participants containing many endpoints
  • 3.7. Eliminated requirement to manually clean up thread resources on platforms that support automatic thread-specific storage (TSS) cleanup
  • 3.8. Improved flow control of fragmented sample repairs
  • 3.9. RTPS messages containing a malformed inline Qos now trigger a warning, to avoid deserialization errors downstream
  • 3.10. Capture periodic DomainParticipant announcements in DISCOVERY logging category to enhance debugging of discovery
  • 3.11. Print incompatible QoS policies in a discovery snapshot for improved discovery debugging
  • 3.12. Updated default value for socket_monitoring_kind to more performant WINDOWS_IOCP value on Windows systems
  • 3.13. Support for new metadata fields in content filter expressions
  • 3.14. InstanceHandle now provides a default constructor
  • 3.15. Parameter type change to more convenient/appropriate size_t in pluggable transport’s to_string APIs
  • 3.16. Deprecations and Removals
    • 3.16.1. “delete” method of DynamicDataTypeSupport deprecated
    • 3.16.2. dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size removed (except for Java)
  • 3.17. Third-Party Software Changes
• 4. What’s Fixed in 7.5.0
  • 4.1. Discovery
    • 4.1.1. [Critical] Undefined behavior when serializing using any of the builtin discovery plugins
    • 4.1.2. [Critical] Incorrect locators used on newly created DataWriters or DataReaders after a Locator Reachability event
    • 4.1.3. [Major] DomainParticipants using SPDP2 and fragmentation of the participant configuration messages failed to complete discovery
    • 4.1.4. [Major] DomainParticipants failed to announce that endpoint was not reachable when internal clock was monotonic and external clock was real-time
    • 4.1.5. [Minor] DomainParticipants using LBED unregistered remote DataWriters when a remote participant was deleted instead of deleting them
  • 4.2. Usability
    • 4.2.1. [Minor] Unnecessary QoS consistency checks for best effort DataWriters
  • 4.3. Transports
    • 4.3.1. [Critical] Shared Memory communications might not have been recovered if a DataReader crashed or was ungracefully killed
  • 4.4. Reliability Protocol and Wire Representation
    • 4.4.1. [Critical] Writer-side filtered samples not always marked as acknowledged when application acknowledgment was used
  • 4.5. Performance and Scalability
    • 4.5.1. [Critical] High CPU usage and delayed events in a DataReader managing many instances of a deleted DataWriter
  • 4.6. Debuggability
    • 4.6.1. [Major] Incorrect source port for some Real-Time WAN Transport packets recorded with network capture
    • 4.6.2. [Trivial] RTI DDS Spy showed unprintable character in help output
  • 4.7. Content Filters and Query Conditions
    • 4.7.1. [Minor] Setting parameters on QueryCondition could have led to slightly inefficient refiltering
  • 4.8. Request-Reply and Remote Procedure Calls
    • 4.8.1. [Minor] Request-reply and RPC readers created without explicitly loading BuiltinQosLib::Pattern.RPC did not set reliability.max_blocking_time to 10 seconds
  • 4.9. Logging
    • 4.9.1. [Trivial] Incorrect informational log messages when adding or removing remote writers in local readers
  • 4.10. APIs (C or Traditional C++)
    • 4.10.1. [Minor] Incorrect return code for DomainParticipant::assert_liveliness API on disabled participant
  • 4.11. APIs (Java)
    • 4.11.1. [Major] Unnecessary memory operations when receiving inherited bounded sequences
    • 4.11.2. [Major] For types with strings, sample size calculation in Java may have overestimated serialized size
  • 4.12. APIs (C# API)
    • 4.12.1. [Trivial] .NET bundle information not displayed in Launcher
  • 4.13. APIs (Python)
    • 4.13.1. [Critical] Incompatibility between Python API and other APIs when using int8 type
    • 4.13.2. [Major] Python API didn’t support reading TopicQuery samples exclusively
    • 4.13.3. [Minor] Python API didn’t provide enumeration to set Real-Time WAN Transport in code
  • 4.14. APIs (Multiple Languages)
    • 4.14.1. [Minor] Some properties no longer accepted LENGTH_UNLIMITED string as a valid value
    • 4.14.2. [Minor] Request-reply and RPC may have used standard PID instead of selected one
  • 4.15. XML Configuration
    • 4.15.1. [Minor] Possible failure when loading an XML file containing a long comment
  • 4.16. Instances
    • 4.16.1. [Major] Failure to register instances of mutable flat data types
  • 4.17. Crashes
    • 4.17.1. [Critical] Stack smashing error when serializing strings with RTI_CDR_SIZEOF_LONG_DOUBLE set to 16 in C++11 in release mode using GCC compiler
    • 4.17.2. [Critical] Possible crash on MIGInterpreter_parse while receiving data at the same time that entities are removed, on architectures with a weak memory model
    • 4.17.3. [Critical] Race condition in RTI Monitoring Library 2.0 caused a crash
    • 4.17.4. [Critical] Segmentation fault if Application Kind contained more than 255 characters when calling RTI_DL_DistLogger_getInstance
    • 4.17.5. [Critical] Potential crash if creation of Publisher or Subscriber failed while database garbage collection process was running
    • 4.17.6. [Critical] Possible crash when calling any write operation on architectures with a weak memory model
    • 4.17.7. [Critical] Stack overflow when parsing very long SQL filter expressions
    • 4.17.8. [Critical] Possible crash when creating DomainParticipants concurrently
    • 4.17.9. [Critical] Crash when writing data on a ContentFilteredTopic in combination with transient durability and delegated reliability
    • 4.17.10. [Major] Possible crash after memory allocation failures
    • 4.17.11. [Major] Using unbounded or very large types with query conditions in Python API could cause crash
    • 4.17.12. [Major] Segmentation fault if application ran out of memory while generating a log message
  • 4.18. Hangs
    • 4.18.1. [Critical] Potential deadlock when using TCP Transport on Windows systems if WINDOWS_WAITFORMULTIPLEOBJECTS was selected as the socket monitoring API
    • 4.18.2. [Major] Potential deadlock when using Durable Writer History if there was a failure while creating the connection
    • 4.18.3. [Major] Potential deadlock when using DynamicData in Debug libraries if TypePlugin initialization failed
    • 4.18.4. [Major] Potential issues using rti.asyncio.run or asyncio.run with dds.DataReader.take_async
    • 4.18.5. [Major] RPC failures when serializing the return value or out/inout parameters caused a timeout on client side
  • 4.19. Memory Leaks/Growth
    • 4.19.1. [Critical] Possible unbounded memory growth on DataReader of keyed type after failing to match with a remote DataWriter
    • 4.19.2. [Critical] Memory leaks and errors when using DynamicDataReaders or FlatData DataReaders plus DDS-fragmentation and compression or encryption
    • 4.19.3. [Critical] Unbounded memory growth when using DynamicDataReaders with multiple data representations and keyed types
    • 4.19.4. [Critical] Unbounded memory growth when using RECOVER instance state consistency and instances were removed from DataReader queue
    • 4.19.5. [Major] Memory leak when parsing invalid module in XML
    • 4.19.6. [Major] Memory leak when using DynamicData with types containing optional members of string aliases or when cloning such types
    • 4.19.7. [Minor] DynamicDataTypeSupport objects not reclaimed by garbage collector
    • 4.19.8. [Minor] Potential DynamicData sample leaked on DataReader deletion
  • 4.20. Data Corruption
    • 4.20.1. [Critical] Potential corruption in samples with sequences of strings when using Traditional C++ API and std::string
    • 4.20.2. [Critical] Rare race condition may have led to undefined behavior
    • 4.20.3. [Major] Possible data corruption when using ISerializer<T> to serialize a sample
  • 4.21. Entities
    • 4.21.1. [Major] Error when setting QoS on Publisher or Subscriber without endpoints
  • 4.22. Interoperability
    • 4.22.1. [Critical] XCDR serialization of a mutable union with a discriminator value that does not select a union member was not compliant with OMG specification
    • 4.22.2. [Critical] RTPS messages containing vendor-specific submessages could have been dropped
    • 4.22.3. [Critical] Multiple RTPS messages received in a single datagram caused issues
  • 4.23. Vulnerabilities
    • 4.23.1. [Critical] Potential stack buffer overflow in Connext applications when parsing an XML type
    • 4.23.2. [Critical] Potential stack buffer write overflow in license-managed Core Libraries when setting RTI_LICENSE_FILE environment variable
    • 4.23.3. [Critical] Buffer write overflow while parsing malicious license file
    • 4.23.4. [Critical] Potential integer overflow in Connext applications on 32-bit systems when parsing XML files with very large number of default attributes or levels of nesting
  • 4.24. Other
    • 4.24.1. [Critical] Data races on architectures with weak memory models
    • 4.24.2. [Major] Printing an IDL union with an enum discriminator could have produced an incorrect output
    • 4.24.3. [Major] Incorrect CPU assignment when using THREAD_SETTINGS_CPU_RR_ROTATION in receiver_pool
    • 4.24.4. [Trivial] Possible data race when creating DomainParticipants
    • 4.24.5. [Trivial] Printing a type with an annotation using an enum produced an incorrect output
• 5. Previous Release
  • 5.1. What’s New in 7.4.0
    • 5.1.1. Set up reliable communications for fragmented data more easily and with better performance, by removing asynchronous publishing requirement
    • 5.1.2. Modern C++ RPC API now fully productized and supported
    • 5.1.3. Discover relevant QoS more easily through categorizations added to API Reference HTML documentation
    • 5.1.4. Easier QoS configuration for Request-Reply and RPC with new built-in QoS profile
    • 5.1.5. Write Python applications faster with reactive subscriptions
    • 5.1.6. New Ping built-in type helps debug and prototype with the Python API
    • 5.1.7. DDS Spy now prints full timestamps (with date and fractions of a second) and epoch timestamps
    • 5.1.8. New DynamicData APIs get and set a union’s discriminator value
    • 5.1.9. Deprecations and Removals
  • 5.2. What’s Fixed in 7.4.0
    • 5.2.1. Discovery
    • 5.2.2. Serialization and Deserialization
    • 5.2.3. Usability
    • 5.2.4. Transports
    • 5.2.5. Reliability Protocol and Wire Representation
    • 5.2.6. Bandwidth Sensitivity
    • 5.2.7. Debuggability
    • 5.2.8. Content Filters and Query Conditions
    • 5.2.9. TopicQueries
    • 5.2.10. Request-Reply and Remote Procedure Calls
    • 5.2.11. Logging
    • 5.2.12. Dynamic Data
    • 5.2.13. APIs (Modern C++ API)
    • 5.2.14. APIs (Java)
    • 5.2.15. APIs (Python)
    • 5.2.16. APIs (Multiple Languages)
    • 5.2.17. XML Configuration
    • 5.2.18. Crashes
    • 5.2.19. Hangs
    • 5.2.20. Memory Leaks/Growth
    • 5.2.21. Data Corruption
    • 5.2.22. OMG Specification Compliance
    • 5.2.23. Interoperability
    • 5.2.24. Vulnerabilities
    • 5.2.25. Other
• 6. Known Issues
  • 6.1. Known Issues with Discovery (SPDP2)
    • 6.1.1. Features under future consideration for SPDP2
    • 6.1.2. Participants using SPDP2 and allow_unauthenticated_participants fail to communicate if only one participant fails authentication
  • 6.2. Known Issues with Serialization and Deserialization
    • 6.2.1. Some parameters cannot be received multiple times within same SPDP sample
    • 6.2.2. Connext not compliant with Extended CDR encoding version 2 for types containing arrays and sequences of non-primitive types
  • 6.3. Known Issues with Usability
    • 6.3.1. Cannot open USER_QOS_PROFILES.xml in rti_workspace/examples from Visual Studio
    • 6.3.2. DataWriter’s Listener callback on_application_acknowledgment() not triggered by late-joining DataReaders
    • 6.3.3. HighThroughput and AutoTuning built-in QoS Profiles may cause communication failure when writing small samples
    • 6.3.4. Memory leak if Foo:initialize() called twice
    • 6.3.5. Wrong error code after timeout on write() from Asynchronous Publisher
    • 6.3.6. Type Consistency enforcement disabled for structs with more than 10000 members
    • 6.3.7. Escaping special characters in regular/filter expressions not supported in some cases
    • 6.3.8. Non-English Unicode (UTF-8) file names and paths not supported
  • 6.4. Known Issues with Code Generation
    • 6.4.1. Examples and generated code for Visual Studio 2017 and later may not compile (Error MSB8036)
  • 6.5. Known Issues with Instance Lifecycle
    • 6.5.1. RECOVER_INSTANCE_STATE_CONSISTENCY setting not fully supported by RTI Infrastructure Services
    • 6.5.2. Persistence Service DataReaders ignore serialized key propagated with dispose updates
    • 6.5.3. instance_state_consistency_kind QoS cannot be modified before containing entity is enabled
  • 6.6. Known Issues with Reliability
    • 6.6.1. DataReaders with different reliability kinds under Subscriber with GROUP_PRESENTATION_QOS may cause communication failure
  • 6.7. Known Issues with Content Filters and Query Conditions
    • 6.7.1. Writer-side filtering may cause missed deadline
    • 6.7.2. filter_sample_* statistics in DDS_DataWriterProtocolStatus not updated correctly
  • 6.8. Known Issues with TopicQueries
    • 6.8.1. TopicQueries not supported with DataWriters configured to use batching or Durable Writer History
  • 6.9. Known Issues with C# API
    • 6.9.1. Connext API
    • 6.9.2. IDL-to-C# Code Generation
    • 6.9.3. API Reference
  • 6.10. Known Issues with Transports
    • 6.10.1. AppAck messages cannot be greater than underlying transport message size
    • 6.10.2. DataReader cannot persist AppAck messages greater than 32767 bytes
    • 6.10.3. Discovery with Connext Micro fails when shared memory transport enabled
    • 6.10.4. Communication may not be reestablished in some IP mobility scenarios
    • 6.10.5. Corrupted samples may be forwarded through Routing Service when using Zero-Copy transfer over shared memory
    • 6.10.6. Network Capture does not support frames larger than 65535 bytes
    • 6.10.7. Shared memory transport in QNX 7.0 and earlier can result in priority inversion
    • 6.10.8. Ungracefully terminated QNX processes using SHMEM transport prevents startup of new processes due to unclosed POSIX semaphores (QNX 7.0 and earlier)
  • 6.11. Known Issues with FlatData
    • 6.11.1. FlatData language bindings do not support automatic initialization of arrays of primitive values to non-zero default values
    • 6.11.2. Flat Data: plain_cast on types with 64-bit integers may cause undefined behavior
  • 6.12. Known Issues with Coherent Sets
    • 6.12.1. Some coherent sets may be lost or reported as incomplete with batching configurations
    • 6.12.2. Copy of SampleInfo::coherent_set_info field is not supported
    • 6.12.3. Other known issues with coherent sets
  • 6.13. Known Issues with Dynamic Data
    • 6.13.1. Conversion of data by member-access primitives limited when converting to types that are not supported on all platforms
    • 6.13.2. Types that contain bit fields not supported
    • 6.13.3. Long double not supported for DynamicData in Java API
  • 6.14. Known Issues with RTI Monitoring Library
    • 6.14.1. Problems with NDDS_Transport_Support_set_builtin_transport_property() if Participant Sends Monitoring Data
    • 6.14.2. Participant’s CPU and memory statistics are per application
    • 6.14.3. ResourceLimit channel_seq_max_length must not be changed
  • 6.15. Other Known Issues
    • 6.15.1. Possible Valgrind still-reachable leaks when loading dynamic libraries
    • 6.15.2. 64-bit discriminator values greater than (2^31-1) or smaller than (-2^31) not supported
    • 6.15.3. Creating multiple DataReaders for the same Topic under the same Subscriber configured with Group Ordered Access is not supported
    • 6.15.4. With DISALLOW_TYPE_COERCION and Types containing unbounded members, other vendor DataWriters/DataReaders will not match Connext DataWriters/DataReaders

• Copyrights and Notices