RTI Connext Migration Guide Logo
6.1.1
  • 1. Upgrade Overview
    • 1.1. Upgrade Path
    • 1.2. Upgrade Steps
    • 1.3. Regenerating and Recompiling
      • 1.3.1. Generated code compatibility
      • 1.3.2. Application Binary Interface
  • 2. Upgrading from 6.1.0 to 6.1.1
    • 2.1. General Compatibility 6.1.1
      • 2.1.1. Potential -fPIC flag issue when using static libraries in Linux and QNX if upgrading from 6.1.0
    • 2.2. Product-Specific Compatibility 6.1.1
      • 2.2.1. RTI Connext DDS Core Libraries
      • 2.2.2. RTI Code Generator
        • 2.2.2.1. C# language binding introduced in 6.1.0 now used by default
      • 2.2.3. RTI System Designer
        • 2.2.3.1. Old types no longer accepted in group_data, user_data, or topic_data field
        • 2.2.3.2. XML file from 6.1.1 may not load in previous releases
      • 2.2.4. RTI Security Plugins
        • 2.2.4.1. Problems checking whether a participant is allowed to exist
  • 3. Upgrading from 6.0.1 to 6.1.0
    • 3.1. General Compatibility 6.1.0
      • 3.1.1. Platforms
        • 3.1.1.1. New and Removed Platforms
        • 3.1.1.2. Linking static Linux or QNX libraries with object files built with -fPIC will fail
        • 3.1.1.3. New Linux® Linker Flag
        • 3.1.1.4. Additional Build Flags for Backtrace Feature
        • 3.1.1.5. VxWorks Installation Changes
        • 3.1.1.6. VxWorks Library Name Changes
      • 3.1.2. Wire Compatibility
        • 3.1.2.1. RTPS Versions
        • 3.1.2.2. Protocol Changes
        • 3.1.2.3. DataReader in previous release cannot receive MultiChannel or TopicQuery RTPS fragmented data from DataWriter in 6.1.0
      • 3.1.3. Type System Compatibility
        • 3.1.3.1. Connext DDS applications from previous releases will not interoperate with 6.1.0 and later, for types containing optional primitive members, when data representation is XCDR2
        • 3.1.3.2. C/C++ applications may not interoperate for keyed types under certain conditions
      • 3.1.4. Transport Compatibility
        • 3.1.4.1. IP Mobility events may stop communication with applications from previous releases
      • 3.1.5. XML Compatibility
        • 3.1.5.1. Summary of XML schema changes for XML-Based Application Creation and QoS profiles
        • 3.1.5.2. Connext DDS 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
        • 3.1.5.3. Use new XML tag names <participant_qos>, <filter>, and <parameter_list>
        • 3.1.5.4. XML fields of type duration have unset tags default to 0 with a warning log message
        • 3.1.5.5. Instance replacement changes affect XML files in Micro Application Generator (MAG)
    • 3.2. Product-Specific Compatibility 6.1.0
      • 3.2.1. RTI Connext DDS Core Libraries
        • 3.2.1.1. Configuration Changes
        • 3.2.1.2. API Changes
        • 3.2.1.3. Library Size
        • 3.2.1.4. Memory Consumption
        • 3.2.1.5. Network Performance
        • 3.2.1.6. Discovery Performance
        • 3.2.1.7. RTI Connext DDS Micro Compatibility
        • 3.2.1.8. Miscellaneous
      • 3.2.2. RTI Code Generator
        • 3.2.2.1. -language C++03 will soon be removed
        • 3.2.2.2. -legacyPlugin option removed
        • 3.2.2.3. Modern C++ API now maps enums to enum class
        • 3.2.2.4. IDL type incompatibility: @key should no longer be set in derived structures
      • 3.2.3. RTI Connext Tools
        • 3.2.3.1. Tools won’t work on some operating systems
        • 3.2.3.2. RTI Launcher: Previous releases could propagate some environment variables on macOS systems
        • 3.2.3.3. RTI Admin Console
        • 3.2.3.4. RTI System Designer
      • 3.2.4. RTI Security Plugins
        • 3.2.4.1. OpenSSL upgrade
        • 3.2.4.2. Target OpenSSL bundles now distributed as .rtipkg files
        • 3.2.4.3. Changed OpenSSL static library names
        • 3.2.4.4. <allow_rule> pattern partitions from previous releases may no longer work
        • 3.2.4.5. No backward interoperability if Permissions Document subject name has commas in an attribute value
        • 3.2.4.6. authentication.crl_file property has been deprecated and replaced by authentication.crl, which requires a “file:” or “data:,” prefix
        • 3.2.4.7. DomainParticipant creation will fail if either logging.distribute.enable or logging.log_file logging property is set
        • 3.2.4.8. Deprecated logging.distribute properties
        • 3.2.4.9. Old logging.distribute.queue threshold property names no longer work
        • 3.2.4.10. Changed default value of max_heartbeat_retries for secure volatile channel to UNLIMITED
        • 3.2.4.11. Improvements in Discovery Performance
      • 3.2.5. RTI Secure WAN Transport
        • 3.2.5.1. OpenSSL upgrade
        • 3.2.5.2. Changed OpenSSL static library names
      • 3.2.6. RTI TLS Support
        • 3.2.6.1. OpenSSL upgrade
        • 3.2.6.2. Changed OpenSSL static library names
        • 3.2.6.3. tls.cipher.cipher_list property has no effect when using TLS 1.3
      • 3.2.7. RTI Infrastructure Services
        • 3.2.7.1. XML Compatibility
        • 3.2.7.2. RTI Routing Service
        • 3.2.7.3. RTI Recording Service
        • 3.2.7.4. RTI Persistence Service
      • 3.2.8. RTI Connext DDS Micro
  • 4. Upgrading from 6.0.0 to 6.0.1
    • 4.1. General Compatibility 6.0.1
      • 4.1.1. Platforms
      • 4.1.2. Wire Changes and Compatibility
        • 4.1.2.1. RTPS Versions
        • 4.1.2.2. Fragmentation is now independent of sample serialized size
      • 4.1.3. Type System Compatibility
        • 4.1.3.1. Wire representation of TypeObject
        • 4.1.3.2. Incompatibility issues for Java and .Net when using XCDR2
      • 4.1.4. Other Compatibility Issues
        • 4.1.4.1. Large data support for Multichannel and TopicQuery has been disabled
    • 4.2. Product-Specific Compatibility 6.0.1
      • 4.2.1. RTI Connext DDS Core Libraries
      • 4.2.2. RTI Code Generator
        • 4.2.2.1. Incompatibility issues for Java and .Net when using XCDR2
        • 4.2.2.2. Invalid XSD file from an IDL/XML file if input file contains a range annotation
      • 4.2.3. RTI Connext DDS Micro
      • 4.2.4. RTI Security Plugins
        • 4.2.4.1. OpenSSL upgrade
        • 4.2.4.2. Changes to building an application
        • 4.2.4.3. Changes to behavior of intermediate certificates
        • 4.2.4.4. Property key_material_key now required for Secure Persistence Service
      • 4.2.5. RTI Secure WAN Transport
        • 4.2.5.1. OpenSSL upgrade
        • 4.2.5.2. Changes to building an application
      • 4.2.6. RTI TLS Support
        • 4.2.6.1. OpenSSL upgrade
        • 4.2.6.2. Changes to building an application
  • 5. Upgrading from 5.3.1 to 6.0.0
    • 5.1. General Compatibility 6.0.0
      • 5.1.1. Platforms
      • 5.1.2. Wire Compatibility
        • 5.1.2.1. RTPS Versions
        • 5.1.2.2. New default GUID generation mode
        • 5.1.2.3. Default shared memory locator has changed
        • 5.1.2.4. 4.2e alignment option deprecated
        • 5.1.2.5. Changed wire representation of TypeObject
        • 5.1.2.6. TypeCode information is not sent by default
      • 5.1.3. Reliability Protocol
        • 5.1.3.1. Changes in behavior of write() operation with KEEP_LAST configuration
      • 5.1.4. Type System Compatibility
        • 5.1.4.1. Migration to Extended CDR encoding version 2 (XCDR2)
        • 5.1.4.2. Changed wire representation of TypeObject
        • 5.1.4.3. TypeCode information is not sent by default
        • 5.1.4.4. Unbounded sequences and strings in XML type representation
        • 5.1.4.5. wchar and wstring language binding changes
        • 5.1.4.6. Properties dds.type_consistency.ignore_member_names and dds.type_consistency.ignore_sequence_bounds have been deprecated
      • 5.1.5. Transport Compatibility
        • 5.1.5.1. Default shared memory locator has changed
        • 5.1.5.2. VxWorks shared-memory transport compatibility
      • 5.1.6. XML Compatibility
        • 5.1.6.1. QoS Profile multiple inheritance
        • 5.1.6.2. XSD issues
      • 5.1.7. Other Compatibility Issues
        • 5.1.7.1. Behavior change when retrieving QoS using topic_name (when there are multiple matching QoSes)
    • 5.2. Product-Specific Compatibility 6.0.0
      • 5.2.1. RTI Connext DDS Core Libraries
        • 5.2.1.1. APIs
        • 5.2.1.2. Generated Code
        • 5.2.1.3. QoS
        • 5.2.1.4. Library Size
        • 5.2.1.5. Memory Consumption
        • 5.2.1.6. Performance
        • 5.2.1.7. RTI Connext DDS Micro Compatibility
      • 5.2.2. RTI Security Plugins
        • 5.2.2.1. Configuration
        • 5.2.2.2. Wire Compatibility
        • 5.2.2.3. APIs
      • 5.2.3. RTI Secure WAN Transport
      • 5.2.4. RTI TLS Support
      • 5.2.5. RTI Ada Language Support
        • 5.2.5.1. APIs
      • 5.2.6. RTI Code Generator
        • 5.2.6.1. Removed -stl Option
        • 5.2.6.2. Removed Support for -notypecode
        • 5.2.6.3. Removed -use42eAlignment
        • 5.2.6.4. Generated code for Extended CDR Encoding Version 2 (XCDR2)
        • 5.2.6.5. Incorrect TypeCode name for member fields whose name was a keyword in Java
        • 5.2.6.6. Modified maximum length of sequences and strings when -unboundedSupport is not used, when converting to XML
        • 5.2.6.7. Traditional C++ compiled with -fno-exceptions
        • 5.2.6.8. Support for new, standard IDL, fixed-width integer types
        • 5.2.6.9. Change in default optimization level for code generation
      • 5.2.7. RTI Connext DDS Micro
        • 5.2.7.1. New Installation Procedure
        • 5.2.7.2. Change In Documentation
        • 5.2.7.3. Application Binary Interface
        • 5.2.7.4. APIs
        • 5.2.7.5. Connext DDS Compatibility
      • 5.2.8. RTI Routing Service
        • 5.2.8.1. Application Binary Interface
        • 5.2.8.2. APIs
        • 5.2.8.3. Configuration
        • 5.2.8.4. Administration and Monitoring
        • 5.2.8.5. QoS
        • 5.2.8.6. Performance
        • 5.2.8.7. Library Size
        • 5.2.8.8. Documentation
      • 5.2.9. RTI Recording Service
        • 5.2.9.1. APIs
        • 5.2.9.2. Configuration
        • 5.2.9.3. Database Format
        • 5.2.9.4. Running Recording Service 5.3.1
        • 5.2.9.5. Documentation
      • 5.2.10. RTI Persistence Service
        • 5.2.10.1. External Database Compatibility
        • 5.2.10.2. Persistent Storage (Database) Format Compatibility
        • 5.2.10.3. Persistence Storage (Database) Locking Compatibility
        • 5.2.10.4. Dynamically Linked Libraries
      • 5.2.11. RTI Database Integration Service
        • 5.2.11.1. Database Compatibility
      • 5.2.12. RTI Cloud Discovery Service
      • 5.2.13. RTI Launcher
        • 5.2.13.1. Configuration
      • 5.2.14. RTI Administration Console
        • 5.2.14.1. New Default GUID Generator Mode
        • 5.2.14.2. New GTK+ and Cairo Dependencies
        • 5.2.14.3. Connext DDS Micro Compatibility
      • 5.2.15. RTI Monitor
      • 5.2.16. RTI Utilities
        • 5.2.16.1. Dynamically Linked Libraries
  • 6. Regressions
    • 6.1. Regressions in 6.1.1
      • 6.1.1. Core Libraries
        • 6.1.1.1. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
        • 6.1.1.2. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
    • 6.2. Regressions in 6.1.0
      • 6.2.1. Core Libraries
        • 6.2.1.1. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
        • 6.2.1.2. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
        • 6.2.1.3. Fixed in 6.1.1
      • 6.2.2. RTI Code Generator
        • 6.2.2.1. Fixed in 6.1.1
      • 6.2.3. RTI Admin Console
        • 6.2.3.1. Fixed in 6.1.1
      • 6.2.4. RTI TLS Support
        • 6.2.4.1. Fixed in 6.1.1
      • 6.2.5. RTI Security Plugins
        • 6.2.5.1. Fixed in 6.1.1
      • 6.2.6. RTI Routing Service
        • 6.2.6.1. Fixed in 6.1.1
    • 6.3. Regressions in 6.0.1
      • 6.3.1. Core Libraries
        • 6.3.1.1. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
        • 6.3.1.2. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
        • 6.3.1.3. Fixed in 6.1.1
        • 6.3.1.4. Fixed in 6.1.0
      • 6.3.2. RTI Code Generator
        • 6.3.2.1. Fixed in 6.1.1
      • 6.3.3. RTI Routing Service
        • 6.3.3.1. Fixed in 6.1.1
        • 6.3.3.2. Fixed in 6.1.0
      • 6.3.4. RTI Recording Service
        • 6.3.4.1. Fixed in 6.1.0
      • 6.3.5. RTI Prototyper
        • 6.3.5.1. Fixed in 6.1.0
    • 6.4. Regressions in 6.0.0
      • 6.4.1. RTI Connext DDS Core Libraries
        • 6.4.1.1. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
        • 6.4.1.2. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
        • 6.4.1.3. Fixed in 6.1.1
        • 6.4.1.4. Fixed in 6.1.0
        • 6.4.1.5. Fixed in 6.0.1
      • 6.4.2. RTI Security Plugins
        • 6.4.2.1. Fixed in 6.0.1
      • 6.4.3. RTI Code Generator
        • 6.4.3.1. Fixed in 6.1.1
        • 6.4.3.2. Fixed in 6.0.1
      • 6.4.4. RTI Routing Service
        • 6.4.4.1. Fixed in 6.1.1
        • 6.4.4.2. Fixed in 6.1.0
        • 6.4.4.3. Fixed in 6.0.1
      • 6.4.5. RTI Recording Service
        • 6.4.5.1. Fixed in 6.0.1
      • 6.4.6. RTI Cloud Discovery Service
        • 6.4.6.1. Fixed in 6.0.1
  • 7. Changes to This Document
  • 8. Copyrights
RTI Connext Migration Guide
  • Docs »
  • 2. Upgrading from 6.1.0 to 6.1.1 »
  • 2.2. Product-Specific Compatibility 6.1.1
  • View page source

2.2. Product-Specific Compatibility 6.1.1¶

After addressing migration issues in Section 2.1, address Core Libraries issues in Section 2.2.1. Then review and address the rest of the product-specific migration issues in this section for Release 6.1.1.

  • 2.2.1. RTI Connext DDS Core Libraries
  • 2.2.2. RTI Code Generator
    • 2.2.2.1. C# language binding introduced in 6.1.0 now used by default
  • 2.2.3. RTI System Designer
    • 2.2.3.1. Old types no longer accepted in group_data, user_data, or topic_data field
    • 2.2.3.2. XML file from 6.1.1 may not load in previous releases
  • 2.2.4. RTI Security Plugins
    • 2.2.4.1. Problems checking whether a participant is allowed to exist
Next Previous

© Copyright 2022, Real-Time Innovations, Inc

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

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