RTI Connext Migration Guide Logo
7.4.0
  • 1. Important: How to Use this Guide
    • 1.1. Upgrade Path
    • 1.2. Upgrade Steps
    • 1.3. Regenerating Code and Updating Your Projects
      • 1.3.1. Generated code compatibility
      • 1.3.2. Updating your projects
        • 1.3.2.1. C and C++ applications
        • 1.3.2.2. Java applications
        • 1.3.2.3. C# applications
        • 1.3.2.4. Python applications
      • 1.3.3. Updating your source code
  • 2. Upgrading from 7.3.0 to 7.4.0
    • 2.1. General Compatibility 7.4.0
      • 2.1.1. Wire Compatibility
        • 2.1.1.1. RTPS Versions
        • 2.1.1.2. Best-effort DataReader from before 6.1.0 cannot receive MultiChannel RTPS fragmented data from synchronous DataWriter in 7.4.0
      • 2.1.2. Transport Compatibility
        • 2.1.2.1. Real-Time WAN Transport updated message_size_max value may cause messages to be dropped from previous versions
    • 2.2. Product-Specific Compatibility 7.4.0
      • 2.2.1. RTI Connext Core Libraries
        • 2.2.1.1. Properties dds.sample_assignability.accept_unknown_enum_value and dds.sample_assignability.accept_unknown_union_discriminator have been deprecated
        • 2.2.1.2. Sample assignability default value changed in from_cdr_buffer APIs
        • 2.2.1.3. Can no longer use “DDS_” prefix with KEEP_LAST_HISTORY_QOS and KEEP_ALL_HISTORY_QOS enumeration values in XML files
        • 2.2.1.4. New discovery protocol APIs for RPC and Request-Reply in Modern C++
      • 2.2.2. RTI Security Plugins
        • 2.2.2.1. Interoperability with DomainParticipants that have a domain tag or partitions
        • 2.2.2.2. HMAC-Only mode removed from the Builtin Security Plugins
        • 2.2.2.3. Use new property in place of authentication.key_establishment_algorithm
      • 2.2.3. RTI Connext Observability Framework
  • 3. Upgrading from 6.1.2 to 7.3.0
    • 3.1. General Compatibility 7.3.0
      • 3.1.1. Wire Compatibility
        • 3.1.1.1. RTPS Versions
        • 3.1.1.2. New default RTPS checksum mechanism
    • 3.2. Product-Specific Compatibility 7.3.0
      • 3.2.1. RTI Connext Core Libraries
        • 3.2.1.1. Deprecations or Removals
        • 3.2.1.2. API Compatibility
        • 3.2.1.3. Configuration Changes
        • 3.2.1.4. Logging Changes
        • 3.2.1.5. Library Size
        • 3.2.1.6. Memory Consumption
        • 3.2.1.7. Network Performance
        • 3.2.1.8. Discovery Performance
        • 3.2.1.9. Transport Compatibility
        • 3.2.1.10. Other Changes
      • 3.2.2. Security Plugins
        • 3.2.2.1. Deprecations or Removals
        • 3.2.2.2. API Compatibility
        • 3.2.2.3. Changes to Building an Application
        • 3.2.2.4. Changes to Shipped Examples
        • 3.2.2.5. Configuration Changes
        • 3.2.2.6. Logging Changes
        • 3.2.2.7. Performance and Scalability
        • 3.2.2.8. Wire Compatibility
      • 3.2.3. RTI TLS Support
        • 3.2.3.1. OpenSSL 3.0 upgrade and 1.1.1 removal
        • 3.2.3.2. Deprecated tls.cipher.dh_param_files
        • 3.2.3.3. New OpenSSL 3 requirement on tls.cipher.cipher_list
      • 3.2.4. RTI Infrastructure Services
        • 3.2.4.1. Use <domain_participant_qos> tag instead of <participant_qos> tag to be compliant with DDS-XML specification
        • 3.2.4.2. Removals in Cloud Discovery Service
        • 3.2.4.3. Persistence Service
      • 3.2.5. RTI Tools
        • 3.2.5.1. Secure BuiltinLoggingTopic renamed to BuiltinLoggingTypeV2
      • 3.2.6. RTI System Designer
        • 3.2.6.1. XML files from 6.1.2 or earlier may not load in release 7.3.0
        • 3.2.6.2. Renamed shared_secret_algorithm to key_establishment_algorithm
      • 3.2.7. RTI Limited Bandwidth Endpoint Discovery Plugin
      • 3.2.8. RTI Connext Micro
        • 3.2.8.1. Connext Micro 3 not compatible with DDS-level fragmentation in Connext Professional 7
        • 3.2.8.2. Connext Professional DataWriter not compatible with Connext Micro/Cert DataReader under certain conditions
  • 4. Upgrading from 6.1.0 to 6.1.2
    • 4.1. General Compatibility 6.1.2
      • 4.1.1. Potential -fPIC flag issue when using static libraries in Linux and QNX if upgrading from 6.1.0
    • 4.2. Product-Specific Compatibility 6.1.2
      • 4.2.1. RTI Connext Core Libraries
        • 4.2.1.1. Removed ability to share a database connection in Persistence Service and durable writer history
        • 4.2.1.2. Upgrading Your C# Projects
        • 4.2.1.3. TopicQuery not Supported in C# API
      • 4.2.2. RTI Code Generator
        • 4.2.2.1. C# language binding introduced in 6.1.0 now used by default
      • 4.2.3. RTI System Designer
        • 4.2.3.1. Old types no longer accepted in group_data, user_data, or topic_data field
        • 4.2.3.2. XML file from 6.1.1 or above may not load in previous releases
      • 4.2.4. Security Plugins
        • 4.2.4.1. Problems checking whether a participant is allowed to exist
        • 4.2.4.2. Failure loading certificates due to missing keyCertSign when a CA has the KeyUsage X.509 V3 extension
      • 4.2.5. RTI Persistence Service
      • 4.2.6. RTI Connext Micro
        • 4.2.6.1. Connext Micro 3.0.3 installation package currently compatible only with Connext 6.0.1 installer
        • 4.2.6.2. Communication failures with reliable Connext Micro 3 or 2.4 DataReader
  • 5. Upgrading from 6.0.1 to 6.1.0
    • 5.1. General Compatibility 6.1.0
      • 5.1.1. Platforms
        • 5.1.1.1. Linking static Linux or QNX libraries with object files built with -fPIC will fail
        • 5.1.1.2. New Linux® Linker Flag
        • 5.1.1.3. Additional Build Flags for Backtrace Feature
        • 5.1.1.4. VxWorks Installation Changes
        • 5.1.1.5. VxWorks Library Name Changes
        • 5.1.1.6. Android Static Libraries no Longer Supported
      • 5.1.2. Wire Compatibility
        • 5.1.2.1. RTPS Versions
        • 5.1.2.2. Protocol Changes
        • 5.1.2.3. DataReader in previous release cannot receive MultiChannel or TopicQuery RTPS fragmented data from DataWriter in 6.1.0
      • 5.1.3. Type System Compatibility
        • 5.1.3.1. Connext applications from previous releases will not interoperate with 6.1.0 and later, for types containing optional primitive members, when data representation is XCDR2
        • 5.1.3.2. C/C++ applications may not interoperate for keyed types under certain conditions
      • 5.1.4. Transport Compatibility
        • 5.1.4.1. IP Mobility events may stop communication with applications from previous releases
      • 5.1.5. XML Compatibility
        • 5.1.5.1. Summary of XML schema changes for XML-Based Application Creation and QoS profiles
        • 5.1.5.2. Connext applications from 6.1.0 and later may fail to parse XML configuration files from previous releases if <group_data>, <user_data>, or <topic_data> tags are used
        • 5.1.5.3. Use new XML tag names <participant_qos>, <filter>, and <parameter_list>
        • 5.1.5.4. XML fields of type duration have unset tags default to 0 with a warning log message
        • 5.1.5.5. Instance replacement changes affect XML files in Micro Application Generator (MAG)
    • 5.2. Product-Specific Compatibility 6.1.0
      • 5.2.1. RTI Connext Core Libraries
        • 5.2.1.1. Configuration Changes
        • 5.2.1.2. API Changes
        • 5.2.1.3. Library Size
        • 5.2.1.4. Memory Consumption
        • 5.2.1.5. Network Performance
        • 5.2.1.6. Discovery Performance
        • 5.2.1.7. RTI Connext Micro Compatibility
        • 5.2.1.8. Miscellaneous
      • 5.2.2. RTI Code Generator
        • 5.2.2.1. -language C++03 will soon be removed
        • 5.2.2.2. -legacyPlugin option removed
        • 5.2.2.3. Modern C++ API now maps enums to enum class
        • 5.2.2.4. IDL type incompatibility: @key should no longer be set in derived structures
      • 5.2.3. RTI Connext Tools
        • 5.2.3.1. Tools won’t work on some operating systems
        • 5.2.3.2. RTI Launcher: Previous releases could propagate some environment variables on macOS systems
        • 5.2.3.3. RTI Admin Console
        • 5.2.3.4. RTI System Designer
      • 5.2.4. Security Plugins
        • 5.2.4.1. OpenSSL upgrade
        • 5.2.4.2. Target OpenSSL bundles now distributed as .rtipkg files
        • 5.2.4.3. Changed OpenSSL static library names
        • 5.2.4.4. <allow_rule> pattern partitions from previous releases may no longer work
        • 5.2.4.5. No backward interoperability if Permissions Document subject name has commas in an attribute value
        • 5.2.4.6. authentication.crl_file property has been deprecated and replaced by authentication.crl, which requires a “file:” or “data:,” prefix
        • 5.2.4.7. DomainParticipant creation will fail if either logging.distribute.enable or logging.log_file logging property is set
        • 5.2.4.8. Deprecated logging.distribute properties
        • 5.2.4.9. Old logging.distribute.queue threshold property names no longer work
        • 5.2.4.10. Changed default value of max_heartbeat_retries for secure volatile channel to UNLIMITED
        • 5.2.4.11. Improvements in Discovery Performance
      • 5.2.5. RTI Secure WAN Transport
        • 5.2.5.1. OpenSSL upgrade
        • 5.2.5.2. Changed OpenSSL static library names
      • 5.2.6. RTI TLS Support
        • 5.2.6.1. OpenSSL upgrade
        • 5.2.6.2. Changed OpenSSL static library names
        • 5.2.6.3. tls.cipher.cipher_list property has no effect when using TLS 1.3
      • 5.2.7. RTI Infrastructure Services
        • 5.2.7.1. XML Compatibility
        • 5.2.7.2. RTI Routing Service
        • 5.2.7.3. RTI Recording Service
        • 5.2.7.4. RTI Persistence Service
      • 5.2.8. RTI Connext Micro
  • 6. Upgrading from 6.0.0 to 6.0.1
    • 6.1. General Compatibility 6.0.1
      • 6.1.1. Wire Compatibility
        • 6.1.1.1. RTPS Versions
        • 6.1.1.2. Fragmentation is now independent of sample serialized size
      • 6.1.2. Type System Compatibility
        • 6.1.2.1. Wire representation of TypeObject
        • 6.1.2.2. Incompatibility issues for Java and .Net when using XCDR2
      • 6.1.3. Other Compatibility Issues
        • 6.1.3.1. Large data support for Multichannel and TopicQuery has been disabled
    • 6.2. Product-Specific Compatibility 6.0.1
      • 6.2.1. RTI Connext Core Libraries
        • 6.2.1.1. Durable Writer History properties prefix must contain “.builtin” substring
        • 6.2.1.2. Durable Writer History properties cannot be set on DomainParticipant
      • 6.2.2. RTI Code Generator
        • 6.2.2.1. Incompatibility issues for Java and .Net when using XCDR2
        • 6.2.2.2. Invalid XSD file from an IDL/XML file if input file contains a range annotation
      • 6.2.3. Security Plugins
        • 6.2.3.1. OpenSSL upgrade
        • 6.2.3.2. Changes to building an application
        • 6.2.3.3. Changes to behavior of intermediate certificates
        • 6.2.3.4. Property key_material_key now required for Secure Persistence Service
        • 6.2.3.5. Issue related to missing keyCertSign when a CA has the KeyUsage X.509 V3 extension
      • 6.2.4. RTI Secure WAN Transport
        • 6.2.4.1. OpenSSL upgrade
        • 6.2.4.2. Changes to building an application
      • 6.2.5. RTI TLS Support
        • 6.2.5.1. OpenSSL upgrade
        • 6.2.5.2. Changes to building an application
  • 7. Upgrading from 5.3.1 to 6.0.0
    • 7.1. General Compatibility 6.0.0
      • 7.1.1. Wire Compatibility
        • 7.1.1.1. RTPS Versions
        • 7.1.1.2. New default GUID generation mode
        • 7.1.1.3. Default shared memory locator has changed
        • 7.1.1.4. 4.2e alignment option deprecated
        • 7.1.1.5. Changed wire representation of TypeObject
        • 7.1.1.6. TypeCode information is not sent by default
      • 7.1.2. Reliability Protocol
        • 7.1.2.1. Changes in behavior of write() operation with KEEP_LAST configuration
      • 7.1.3. Type System Compatibility
        • 7.1.3.1. Migration to Extended CDR encoding version 2 (XCDR2)
        • 7.1.3.2. Changed wire representation of TypeObject
        • 7.1.3.3. TypeCode information is not sent by default
        • 7.1.3.4. Unbounded sequences and strings in XML type representation
        • 7.1.3.5. wchar and wstring language binding changes
        • 7.1.3.6. Properties dds.type_consistency.ignore_member_names and dds.type_consistency.ignore_sequence_bounds have been deprecated
      • 7.1.4. Transport Compatibility
        • 7.1.4.1. Default shared memory locator has changed
        • 7.1.4.2. VxWorks shared-memory transport compatibility
      • 7.1.5. XML Compatibility
        • 7.1.5.1. QoS Profile multiple inheritance
        • 7.1.5.2. XSD issues
      • 7.1.6. Other Compatibility Issues
        • 7.1.6.1. Behavior change when retrieving QoS using topic_name (when there are multiple matching QoSes)
    • 7.2. Product-Specific Compatibility 6.0.0
      • 7.2.1. RTI Connext Core Libraries
        • 7.2.1.1. APIs
        • 7.2.1.2. Generated Code
        • 7.2.1.3. QoS
        • 7.2.1.4. Library Size
        • 7.2.1.5. Memory Consumption
        • 7.2.1.6. Performance
        • 7.2.1.7. RTI Connext Micro Compatibility
      • 7.2.2. Security Plugins
        • 7.2.2.1. Configuration
        • 7.2.2.2. Wire Compatibility
        • 7.2.2.3. APIs
      • 7.2.3. RTI Secure WAN Transport
      • 7.2.4. RTI TLS Support
      • 7.2.5. RTI Ada Language Support
        • 7.2.5.1. APIs
      • 7.2.6. RTI Code Generator
        • 7.2.6.1. Removed -stl Option
        • 7.2.6.2. Removed Support for -notypecode
        • 7.2.6.3. Removed -use42eAlignment
        • 7.2.6.4. Generated code for Extended CDR Encoding Version 2 (XCDR2)
        • 7.2.6.5. Incorrect TypeCode name for member fields whose name was a keyword in Java
        • 7.2.6.6. Modified maximum length of sequences and strings when -unboundedSupport is not used, when converting to XML
        • 7.2.6.7. Traditional C++ compiled with -fno-exceptions
        • 7.2.6.8. Support for new, standard IDL, fixed-width integer types
        • 7.2.6.9. Change in default optimization level for code generation
      • 7.2.7. RTI Connext Micro
        • 7.2.7.1. New Installation Procedure
        • 7.2.7.2. Change In Documentation
        • 7.2.7.3. Application Binary Interface
        • 7.2.7.4. APIs
        • 7.2.7.5. Connext Compatibility
      • 7.2.8. RTI Routing Service
        • 7.2.8.1. Application Binary Interface
        • 7.2.8.2. APIs
        • 7.2.8.3. Configuration
        • 7.2.8.4. Administration and Monitoring
        • 7.2.8.5. QoS
        • 7.2.8.6. Performance
        • 7.2.8.7. Library Size
        • 7.2.8.8. Documentation
      • 7.2.9. RTI Recording Service
        • 7.2.9.1. APIs
        • 7.2.9.2. Configuration
        • 7.2.9.3. Database Format
        • 7.2.9.4. Running Recording Service 5.3.1
        • 7.2.9.5. Documentation
      • 7.2.10. RTI Persistence Service
        • 7.2.10.1. External Database Compatibility
        • 7.2.10.2. Persistent Storage (Database) Format Compatibility
        • 7.2.10.3. Persistence Storage (Database) Locking Compatibility
        • 7.2.10.4. Dynamically Linked Libraries
      • 7.2.11. RTI Database Integration Service
        • 7.2.11.1. Database Compatibility
      • 7.2.12. RTI Cloud Discovery Service
      • 7.2.13. RTI Launcher
        • 7.2.13.1. Configuration
      • 7.2.14. RTI Administration Console
        • 7.2.14.1. New Default GUID Generator Mode
        • 7.2.14.2. New GTK+ and Cairo Dependencies
        • 7.2.14.3. Connext Micro Compatibility
      • 7.2.15. RTI Monitor
      • 7.2.16. RTI Utilities
        • 7.2.16.1. Dynamically Linked Libraries
  • 8. Regressions
    • 8.1. Regressions in 7.4.0
    • 8.2. Regressions in 7.3.0
      • 8.2.1. Crash on DDS_DomainParticipantFactory_finalize_instance when using XML-Based Application Creation
    • 8.3. Regressions in 7.2.0
      • 8.3.1. Core Libraries
        • 8.3.1.1. Sentinel constant for “invalid” Time contained unexpected value
        • 8.3.1.2. Error message printed for each filtered sample when using writer-side filtering, FlatData, and Zero Copy over shared memory
        • 8.3.1.3. RTI Monitor unable to start due to missing nddsjava.jar in rti_connext_dds-7.2.0/lib/java in LM bundles
      • 8.3.2. Security Plugins
        • 8.3.2.1. Verbosity of security-related messages is per application
    • 8.4. Regressions in 7.1.0
      • 8.4.1. Core Libraries
        • 8.4.1.1. Possible crash when creating DomainParticipants concurrently
        • 8.4.1.2. Potential bus error when calling print and to_string APIs in TypeCode
        • 8.4.1.3. Running rtisetenv_<arch>.bat caused issues in PATH environment
        • 8.4.1.4. Instance purging based on source timestamp does not work
      • 8.4.2. Code Generator
        • 8.4.2.1. Code not stored in specified output directory on Windows when IDL was in a Symlink
        • 8.4.2.2. Command-line option tips not printed if you entered an invalid option
        • 8.4.2.3. Include flag used without a space caused Code Generator to fail
    • 8.5. Regressions in 7.0.0
      • 8.5.1. Core Libraries
        • 8.5.1.1. Some properties no longer accept LENGTH_UNLIMITED string as valid value
        • 8.5.1.2. Possible segmentation fault while enabling a DataWriter that enables batching
        • 8.5.1.3. Running out of memory during DomainParticipant creation causes DomainParticipantFactory finalization to hang
        • 8.5.1.4. Arbitrary read access while parsing malicious RTPS message
        • 8.5.1.5. DDS fragmentation leads to more fragments than expected for a sample
        • 8.5.1.6. TCP transport debug library in Windows does not work with IOCP socket monitoring
      • 8.5.2. Security Plugins
        • 8.5.2.1. Segmentation fault in Java while enabling a DataWriter that protects payloads and enables batching
        • 8.5.2.2. Unexpected “Fragment data not supported by this writer” error when using Security
        • 8.5.2.3. Session keys not renewed as often as they should when using RTPS SIGN protection
      • 8.5.3. Persistence Service
        • 8.5.3.1. Persistence Service XSD schema broken
    • 8.6. Regressions in 6.1.1/6.1.2
      • 8.6.1. Core Libraries
        • 8.6.1.1. Stack smashing error when serializing strings with RTI_CDR_SIZEOF_LONG_DOUBLE set to 16 in C++11 in release mode using GCC compiler
        • 8.6.1.2. Reliable DataReader may stop receiving samples from DataWriter using durable writer history and DDS fragmentation
        • 8.6.1.3. Unexpected precondition error with debug libraries on a reliable DataWriter while sending a GAP
        • 8.6.1.4. Unexpected warning during discovery when multicast disabled
      • 8.6.2. Security Plugins
        • 8.6.2.1. Lack of origin authentication led to unnecessary allocation and possible discovery failure
        • 8.6.2.2. Potential crash while decoding protected submessages
      • 8.6.3. Persistence Service
        • 8.6.3.1. Vulnerability: Stack buffer write overflow while parsing malicious environment variable on non-Windows systems
      • 8.6.4. Limited Bandwidth Plugins
        • 8.6.4.1. Limited Bandwidth ZRTPS transport crashes if an external compression library fails to load
    • 8.7. Regressions in 6.1.0
      • 8.7.1. Core Libraries
        • 8.7.1.1. Possible memory leak when initializing and finalizing the DomainParticipantFactory concurrently
        • 8.7.1.2. max_samples resource limit not honored in some cases when using an unkeyed Topic and TopicQueries
        • 8.7.1.3. DomainParticipant with non-default metatraffic_transport_priority QoS does not complete discovery
        • 8.7.1.4. Broken communication when DataWriter with transport priority discovers DataReader with multicast receive address
        • 8.7.1.5. No more than 100 asynchronous publisher threads can be created
        • 8.7.1.6. Linking static Linux or QNX libraries with object files built with -fPIC will fail
        • 8.7.1.7. Invalid serialization of samples with types containing nested structures with primitive members that require padding
        • 8.7.1.8. Significant performance degradation when using MultiChannel DataWriters
        • 8.7.1.9. Significant performance regression on Windows when using OpenSSL 1.1.1 libraries in 6.1.0
        • 8.7.1.10. ReadCondition may incorrectly stay enabled after sample in READ sample state removed from the DataReader’s queue
        • 8.7.1.11. Missing SampleInfo.ReceptionTimestamp property (C# API only)
      • 8.7.2. Code Generator
        • 8.7.2.1. Java subscriber may not preserve union discriminator value, when discriminator is enum
        • 8.7.2.2. Compile-time error when using -constructor with types containing sequence of pointers
        • 8.7.2.3. Invalid serialization of samples with types containing nested structures with primitive members that require padding
      • 8.7.3. Admin Console
        • 8.7.3.1. High CPU usage by Admin Console
      • 8.7.4. TLS Support
        • 8.7.4.1. hello_world_tcp example root and intermediate CAs expire too early
        • 8.7.4.2. Significant performance regression on Windows when using OpenSSL 1.1.1 libraries in 6.1.0
      • 8.7.5. Security Plugins
        • 8.7.5.1. Significant performance regression on Windows when using OpenSSL 1.1.1 libraries in 6.1.0
        • 8.7.5.2. use_530_partitions incorrectly allowed any non-empty partitions
        • 8.7.5.3. Permissions document incorrectly disallowed unescaped special characters in a subject name
      • 8.7.6. Routing Service
        • 8.7.6.1. Routing Service Socket Adapter example does not properly resolve hostname
        • 8.7.6.2. Crash in Routing Service executable when providing the same -Dname=value pair twice
      • 8.7.7. Recording Service
        • 8.7.7.1. <content_filter> tags did not work for Topic groups
        • 8.7.7.2. Exception reported when recording or replaying type registered as a union
      • 8.7.8. Cloud Discovery Service
        • 8.7.8.1. Restricting domains using command-line arguments requires use of both -allowDomain and -denyDomain arguments
    • 8.8. Regressions in 6.0.1
      • 8.8.1. Core Libraries
        • 8.8.1.1. Samples lost if multiple readers were created in same locator and push_on_write was set to false
        • 8.8.1.2. XML parser crashed from infinite recursion when XML QoS configuration contained inheritance loop
        • 8.8.1.3. Possible issues with communication and enabling DomainParticipant on Windows systems if network interface had multiple IP addresses
        • 8.8.1.4. Failure to allocate memory larger than 2 GB
      • 8.8.2. Recording Service
        • 8.8.2.1. Crash if monitoring enabled and TopicGroup matched with Topic name containing ‘/’ character
      • 8.8.3. Prototyper
        • 8.8.3.1. Prototyper broken in 6.0.1
    • 8.9. Regressions in 6.0.0
      • 8.9.1. Core Libraries
        • 8.9.1.1. XCDR serialization of a mutable union with an unknown discriminator value is not compliant with OMG specification
        • 8.9.1.2. Participant may receive RTPS traffic over SHMEM transport not intended for participant
        • 8.9.1.3. Instance handling on a DataReader and filtering operations in ContentFilteredTopics, QueryConditions, TopicQueries, and Multi-Channel DataWriters may fail
        • 8.9.1.4. Creating DynamicDataTypePlugin with TypeCode from discovery and using content filtering causes segmentation fault
        • 8.9.1.5. Crash with NULL listeners and non-none status masks in C applications that mix types with and without Zero Copy
        • 8.9.1.6. Application using Monitoring Libraries produces segmentation fault during DataReader creation
        • 8.9.1.7. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
        • 8.9.1.8. XSD issue: order enforced in <publisher> tag
        • 8.9.1.9. Invalid key deserialization for mutable derived types with key members
        • 8.9.1.10. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
        • 8.9.1.11. Unexpected log message when calling DataWriter::get_matched_subscription_data or DataReader::get_matched_publication_data on unmatched endpoints
        • 8.9.1.12. XSD issues
        • 8.9.1.13. Dynamic Data issues
        • 8.9.1.14. Discovery does not complete, and there is no error
        • 8.9.1.15. Crash when deserialized_type_object_dynamic_allocation_threshold set to 0
        • 8.9.1.16. Wrong return code for DDS::DataWriter::get_matched_subscription_data and DDS::DataReader::get_matched_publication_data
        • 8.9.1.17. DataReader reports incorrect sample lost and rejected when receiving coherent set
        • 8.9.1.18. QoS policies not resolved to correct values
      • 8.9.2. Security Plugins
        • 8.9.2.1. Discovery time scales poorly
        • 8.9.2.2. Possible lack of SUBSCRIPTION_MATCHED_STATUS if a DataWriter loses liveliness with the DataReader
        • 8.9.2.3. Applications directly calling OpenSSL APIs after DomainParticipant deletion may crash
        • 8.9.2.4. DataWriter does not report PUBLICATION_MATCHED_STATUS for DataReaders that are inactive when it receives their key material
      • 8.9.3. Code Generator
        • 8.9.3.1. Change in behavior in C and traditional C++ for sequences of bounded strings under certain conditions when code is generated with optimization level 1 or 2
        • 8.9.3.2. Invalid key deserialization for mutable derived types with key members
        • 8.9.3.3. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
        • 8.9.3.4. Invalid serialization of samples with types containing primitive members that require padding
        • 8.9.3.5. Java exception during serialization/deserialization of keyed types whose key is an unkeyed nested type with unbounded members
        • 8.9.3.6. Incorrect deserialization in .Net of samples from certain types when published from a writer with disable_inline_keyhash set to true
        • 8.9.3.7. Generated code in traditional C++ with namespaces for an IDL containing a nested module called “rti” will not compile
      • 8.9.4. Routing Service
        • 8.9.4.1. Unbounded memory growth when restarting Service or creating/deleting DomainRoutes
        • 8.9.4.2. Create method in Service API fails to parse XML snippets that start with ‘str://’
        • 8.9.4.3. Executable ignores logging QoS
      • 8.9.5. Recording Service
        • 8.9.5.1. Segmentation fault after discovering application that used UserData QoS Policy
        • 8.9.5.2. Legacy deserialized database table cannot be replayed or converted if it contains compact byte sequences or arrays
        • 8.9.5.3. Segmentation fault in Replay Service or Converter if recorded topics have “::” in their names
      • 8.9.6. Cloud Discovery Service
        • 8.9.6.1. Cloud Discovery Service executable did not log build ID for DDS libraries
  • 9. Changes to This Document
  • 10. Copyrights and Notices
RTI Connext Migration Guide
  • Search

© Copyright 2019-2024, Real-Time Innovations, Inc.

Built with Sphinx using a theme provided by Read the Docs.

Send feedback about this document to documentation@rti.com.