4. Upgrading from 6.0.1 to 6.1.0

See Important: How to Use this Guide, if you haven’t already.

• 4.1. General Compatibility 6.1.0
  • 4.1.1. Platforms
    • 4.1.1.1. Linking static Linux or QNX libraries with object files built with -fPIC will fail
    • 4.1.1.2. New Linux® Linker Flag
    • 4.1.1.3. Additional Build Flags for Backtrace Feature
    • 4.1.1.4. VxWorks Installation Changes
    • 4.1.1.5. VxWorks Library Name Changes
    • 4.1.1.6. Android Static Libraries no Longer Supported
  • 4.1.2. Wire Compatibility
    • 4.1.2.1. RTPS Versions
    • 4.1.2.2. Protocol Changes
    • 4.1.2.3. DataReader in previous release cannot receive MultiChannel or TopicQuery RTPS fragmented data from DataWriter in 6.1.0
  • 4.1.3. Type System Compatibility
    • 4.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
    • 4.1.3.2. C/C++ applications may not interoperate for keyed types under certain conditions
  • 4.1.4. Transport Compatibility
    • 4.1.4.1. IP Mobility events may stop communication with applications from previous releases
  • 4.1.5. XML Compatibility
    • 4.1.5.1. Summary of XML schema changes for XML-Based Application Creation and QoS profiles
    • 4.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
    • 4.1.5.3. Use new XML tag names <participant_qos>, <filter>, and <parameter_list>
    • 4.1.5.4. XML fields of type duration have unset tags default to 0 with a warning log message
    • 4.1.5.5. Instance replacement changes affect XML files in Micro Application Generator (MAG)
• 4.2. Product-Specific Compatibility 6.1.0
  • 4.2.1. RTI Connext Core Libraries
    • 4.2.1.1. Configuration Changes
    • 4.2.1.2. API Changes
    • 4.2.1.3. Library Size
    • 4.2.1.4. Memory Consumption
    • 4.2.1.5. Network Performance
    • 4.2.1.6. Discovery Performance
    • 4.2.1.7. RTI Connext Micro Compatibility
    • 4.2.1.8. Miscellaneous
  • 4.2.2. RTI Code Generator
    • 4.2.2.1. -language C++03 will soon be removed
    • 4.2.2.2. -legacyPlugin option removed
    • 4.2.2.3. Modern C++ API now maps enums to enum class
    • 4.2.2.4. IDL type incompatibility: @key should no longer be set in derived structures
  • 4.2.3. RTI Connext Tools
    • 4.2.3.1. Tools won’t work on some operating systems
    • 4.2.3.2. RTI Launcher: Previous releases could propagate some environment variables on macOS systems
    • 4.2.3.3. RTI Admin Console
    • 4.2.3.4. RTI System Designer
  • 4.2.4. Security Plugins
    • 4.2.4.1. OpenSSL upgrade
    • 4.2.4.2. Target OpenSSL bundles now distributed as .rtipkg files
    • 4.2.4.3. Changed OpenSSL static library names
    • 4.2.4.4. <allow_rule> pattern partitions from previous releases may no longer work
    • 4.2.4.5. No backward interoperability if Permissions Document subject name has commas in an attribute value
    • 4.2.4.6. authentication.crl_file property has been deprecated and replaced by authentication.crl, which requires a “file:” or “data:,” prefix
    • 4.2.4.7. DomainParticipant creation will fail if either logging.distribute.enable or logging.log_file logging property is set
    • 4.2.4.8. Deprecated logging.distribute properties
    • 4.2.4.9. Old logging.distribute.queue threshold property names no longer work
    • 4.2.4.10. Changed default value of max_heartbeat_retries for secure volatile channel to UNLIMITED
    • 4.2.4.11. Improvements in Discovery Performance
  • 4.2.5. RTI Secure WAN Transport
    • 4.2.5.1. OpenSSL upgrade
    • 4.2.5.2. Changed OpenSSL static library names
  • 4.2.6. RTI TLS Support
    • 4.2.6.1. OpenSSL upgrade
    • 4.2.6.2. Changed OpenSSL static library names
    • 4.2.6.3. tls.cipher.cipher_list property has no effect when using TLS 1.3
  • 4.2.7. RTI Infrastructure Services
    • 4.2.7.1. XML Compatibility
    • 4.2.7.2. RTI Routing Service
    • 4.2.7.3. RTI Recording Service
    • 4.2.7.4. RTI Persistence Service
  • 4.2.8. RTI Connext Micro