RTI Connext Migration Guide Logo
7.7.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.1 to 7.7.0
    • 2.1. General Compatibility 7.7.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.7.0
        • 2.1.1.3. DataReader in 7.7.0 may not interoperate with DataWriter in previous release when using XCDR and mutable unions
        • 2.1.1.4. Configure compatibility with Java keyhash calculation in previous releases
        • 2.1.1.5. RTPS Header Extension timestamp clock has changed
        • 2.1.1.6. Wire interoperability issue related to new discovery protocol APIs for RPC and Request-Reply
      • 2.1.2. Type System Compatibility
        • 2.1.2.1. Assignability of 8-bit types
        • 2.1.2.2. Incompatibility between Python API and other APIs when using int8 type
        • 2.1.2.3. Union discriminator initialization change
        • 2.1.2.4. Recursive Type Support
        • 2.1.2.5. TypeObject v1 no longer propagated by default
        • 2.1.2.6. Multiple Calls to Builtin Listeners
        • 2.1.2.7. Requirement for request_types_filter
      • 2.1.3. Transport Compatibility
        • 2.1.3.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.7.0
      • 2.2.1. RTI Connext Core Libraries
        • 2.2.1.1. API Compatibility
        • 2.2.1.2. Configuration Changes
        • 2.2.1.3. Logging Changes
        • 2.2.1.4. Utilities Changes
        • 2.2.1.5. Library Size
        • 2.2.1.6. Memory Consumption
      • 2.2.2. RTI Code Generator
        • 2.2.2.1. Changed default mapping for Modern C++ to “IDL4 to C++”
      • 2.2.3. RTI Security Plugins
        • 2.2.3.1. Wire Compatibility
        • 2.2.3.2. Changes to Building an Application
        • 2.2.3.3. Configuration Changes
        • 2.2.3.4. Key Revision Changes
        • 2.2.3.5. API Changes
        • 2.2.3.6. Logging Changes
        • 2.2.3.7. Deprecation and Removal Changes
        • 2.2.3.8. SDK Changes
      • 2.2.4. RTI Infrastructure Services
        • 2.2.4.1. RTI Persistence Service
        • 2.2.4.2. Routing Service
        • 2.2.4.3. Web Integration Service
      • 2.2.5. RTI Connext Observability Framework
        • 2.2.5.1. Monitoring Library 2.0 incompatible with earlier Collector Service versions
        • 2.2.5.2. Changes to domain ID and domain tag for observability traffic
        • 2.2.5.3. Monitoring Library 2.0 security now enforced when using RTI Security plugins
        • 2.2.5.4. Setting monitoring.telemetry_data.metrics in a derived profile or using an XML snippet now behaves differently
        • 2.2.5.5. Default metrics reduction in Monitoring Library 2.0
        • 2.2.5.6. Disallow unrealistic values of polling_period
        • 2.2.5.7. Monitoring Library 2.0 may require increasing participant_property_string_max_length with LM bundles
  • 3. Upgrading from 7.3.0 to 7.3.1
    • 3.1. General Compatibility 7.3.1
      • 3.1.1. Wire Compatibility
        • 3.1.1.1. RTPS Versions
        • 3.1.1.2. New requirement if you interoperate with DDS vendors that produce multiple RTPS messages in a single datagram
    • 3.2. Product-Specific Compatibility 7.3.1
      • 3.2.1. RTI Connext Core Libraries
        • 3.2.1.1. socket_monitoring_kind default changed to POLL
      • 3.2.2. RTI Security Plugins
        • 3.2.2.1. Changes to Building an Application
        • 3.2.2.2. Configuration Changes
        • 3.2.2.3. Security Plugins SDK
      • 3.2.3. RTI Infrastructure Services
        • 3.2.3.1. Persistence Service
        • 3.2.3.2. Web Integration Service
      • 3.2.4. RTI TLS Support
        • 3.2.4.1. OpenSSL 3 upgrade
      • 3.2.5. RTI Connext Observability Framework
        • 3.2.5.1. Disallow unrealistic values of polling_period
  • 4. Upgrading from 6.1.2 to 7.3.0
    • 4.1. General Compatibility 7.3.0
      • 4.1.1. Wire Compatibility
        • 4.1.1.1. RTPS Versions
        • 4.1.1.2. New default RTPS checksum mechanism
    • 4.2. Product-Specific Compatibility 7.3.0
      • 4.2.1. RTI Connext Core Libraries
        • 4.2.1.1. Deprecations or Removals
        • 4.2.1.2. API Compatibility
        • 4.2.1.3. Configuration Changes
        • 4.2.1.4. Logging Changes
        • 4.2.1.5. Library Size
        • 4.2.1.6. Memory Consumption
        • 4.2.1.7. Network Performance
        • 4.2.1.8. Discovery Performance
        • 4.2.1.9. Transport Compatibility
        • 4.2.1.10. Other Changes
      • 4.2.2. RTI Code Generator
      • 4.2.3. Security Plugins
        • 4.2.3.1. Deprecations or Removals
        • 4.2.3.2. API Compatibility
        • 4.2.3.3. Changes to Building an Application
        • 4.2.3.4. Changes to Shipped Examples
        • 4.2.3.5. Configuration Changes
        • 4.2.3.6. Logging Changes
        • 4.2.3.7. Performance and Scalability
        • 4.2.3.8. Wire Compatibility
      • 4.2.4. RTI TLS Support
        • 4.2.4.1. OpenSSL 3.0 upgrade and 1.1.1 removal
        • 4.2.4.2. Deprecated tls.cipher.dh_param_files
        • 4.2.4.3. New OpenSSL 3 requirement on tls.cipher.cipher_list
      • 4.2.5. RTI Infrastructure Services
        • 4.2.5.1. Use <domain_participant_qos> tag instead of <participant_qos> tag to be compliant with DDS-XML specification
        • 4.2.5.2. Removals in Cloud Discovery Service
        • 4.2.5.3. Persistence Service
      • 4.2.6. RTI Tools
        • 4.2.6.1. Secure BuiltinLoggingTopic renamed to BuiltinLoggingTypeV2
      • 4.2.7. RTI System Designer
        • 4.2.7.1. XML files from 6.1.2 or earlier may not load in release 7.3.0
        • 4.2.7.2. Renamed shared_secret_algorithm to key_establishment_algorithm
      • 4.2.8. RTI Limited Bandwidth Endpoint Discovery Plugin
      • 4.2.9. RTI Connext Micro
        • 4.2.9.1. Connext Micro 3 not compatible with DDS-level fragmentation in Connext Professional 7
        • 4.2.9.2. Connext Professional DataWriter not compatible with Connext Micro/Cert DataReader under certain conditions
  • 5. Upgrading from 6.1.0 to 6.1.2
    • 5.1. General Compatibility 6.1.2
      • 5.1.1. Potential -fPIC flag issue when using static libraries in Linux and QNX if upgrading from 6.1.0
    • 5.2. Product-Specific Compatibility 6.1.2
      • 5.2.1. RTI Connext Core Libraries
        • 5.2.1.1. Removed ability to share a database connection in Persistence Service and durable writer history
        • 5.2.1.2. Upgrading Your C# Projects
        • 5.2.1.3. TopicQuery not Supported in C# API
      • 5.2.2. RTI Code Generator
        • 5.2.2.1. C# language binding introduced in 6.1.0 now used by default
      • 5.2.3. RTI System Designer
        • 5.2.3.1. Old types no longer accepted in group_data, user_data, or topic_data field
        • 5.2.3.2. XML file from 6.1.1 or above may not load in previous releases
      • 5.2.4. Security Plugins
        • 5.2.4.1. Problems checking whether a participant is allowed to exist
        • 5.2.4.2. Failure loading certificates due to missing keyCertSign when a CA has the KeyUsage X.509 V3 extension
      • 5.2.5. RTI Persistence Service
      • 5.2.6. RTI Connext Micro
        • 5.2.6.1. Connext Micro 3.0.3 installation package currently compatible only with Connext 6.0.1 installer
        • 5.2.6.2. Communication failures with reliable Connext Micro 3 or 2.4 DataReader
  • 6. Upgrading from 6.0.1 to 6.1.0
    • 6.1. General Compatibility 6.1.0
      • 6.1.1. Platforms
        • 6.1.1.1. Linking static Linux or QNX libraries with object files built with -fPIC will fail
        • 6.1.1.2. New Linux® Linker Flag
        • 6.1.1.3. Additional Build Flags for Backtrace Feature
        • 6.1.1.4. VxWorks Installation Changes
        • 6.1.1.5. VxWorks Library Name Changes
        • 6.1.1.6. Android Static Libraries no Longer Supported
      • 6.1.2. Wire Compatibility
        • 6.1.2.1. RTPS Versions
        • 6.1.2.2. Protocol Changes
        • 6.1.2.3. DataReader in previous release cannot receive MultiChannel or TopicQuery RTPS fragmented data from DataWriter in 6.1.0
      • 6.1.3. Type System Compatibility
        • 6.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
        • 6.1.3.2. C/C++ applications may not interoperate for keyed types under certain conditions
      • 6.1.4. Transport Compatibility
        • 6.1.4.1. IP Mobility events may stop communication with applications from previous releases
      • 6.1.5. XML Compatibility
        • 6.1.5.1. Summary of XML schema changes for XML-Based Application Creation and QoS profiles
        • 6.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
        • 6.1.5.3. Use new XML tag names <participant_qos>, <filter>, and <parameter_list>
        • 6.1.5.4. XML fields of type duration have unset tags default to 0 with a warning log message
        • 6.1.5.5. Instance replacement changes affect XML files in Micro Application Generator (MAG)
    • 6.2. Product-Specific Compatibility 6.1.0
      • 6.2.1. RTI Connext Core Libraries
        • 6.2.1.1. Configuration Changes
        • 6.2.1.2. API Compatibility
        • 6.2.1.3. Library Size
        • 6.2.1.4. Memory Consumption
        • 6.2.1.5. Network Performance
        • 6.2.1.6. Discovery Performance
        • 6.2.1.7. RTI Connext Micro Compatibility
        • 6.2.1.8. Miscellaneous
      • 6.2.2. RTI Code Generator
        • 6.2.2.1. -language C++03 will soon be removed
        • 6.2.2.2. -legacyPlugin option removed
        • 6.2.2.3. Modern C++ API now maps enums to enum class
        • 6.2.2.4. IDL type incompatibility: @key should no longer be set in derived structures
      • 6.2.3. RTI Connext Tools
        • 6.2.3.1. Tools won’t work on some operating systems
        • 6.2.3.2. RTI Launcher: Previous releases could propagate some environment variables on macOS systems
        • 6.2.3.3. RTI Admin Console
        • 6.2.3.4. RTI System Designer
      • 6.2.4. Security Plugins
        • 6.2.4.1. OpenSSL upgrade
        • 6.2.4.2. Target OpenSSL bundles now distributed as .rtipkg files
        • 6.2.4.3. Changed OpenSSL static library names
        • 6.2.4.4. <allow_rule> pattern partitions from previous releases may no longer work
        • 6.2.4.5. No backward interoperability if Permissions Document subject name has commas in an attribute value
        • 6.2.4.6. authentication.crl_file property has been deprecated and replaced by authentication.crl, which requires a “file:” or “data:,” prefix
        • 6.2.4.7. DomainParticipant creation will fail if either logging.distribute.enable or logging.log_file logging property is set
        • 6.2.4.8. Deprecated logging.distribute properties
        • 6.2.4.9. Old logging.distribute.queue threshold property names no longer work
        • 6.2.4.10. Changed default value of max_heartbeat_retries for secure volatile channel to UNLIMITED
        • 6.2.4.11. Improvements in Discovery Performance
      • 6.2.5. RTI Secure WAN Transport
        • 6.2.5.1. OpenSSL upgrade
        • 6.2.5.2. Changed OpenSSL static library names
      • 6.2.6. RTI TLS Support
        • 6.2.6.1. OpenSSL upgrade
        • 6.2.6.2. Changed OpenSSL static library names
        • 6.2.6.3. tls.cipher.cipher_list property has no effect when using TLS 1.3
      • 6.2.7. RTI Infrastructure Services
        • 6.2.7.1. XML Compatibility
        • 6.2.7.2. RTI Routing Service
        • 6.2.7.3. RTI Recording Service
        • 6.2.7.4. RTI Persistence Service
      • 6.2.8. RTI Connext Micro
  • 7. Upgrading from 6.0.0 to 6.0.1
    • 7.1. General Compatibility 6.0.1
      • 7.1.1. Wire Compatibility
        • 7.1.1.1. RTPS Versions
        • 7.1.1.2. Fragmentation is now independent of sample serialized size
      • 7.1.2. Type System Compatibility
        • 7.1.2.1. Wire representation of TypeObject
        • 7.1.2.2. Incompatibility issues for Java and .Net when using XCDR2
      • 7.1.3. Other Compatibility Issues
        • 7.1.3.1. Large data support for Multichannel and TopicQuery has been disabled
    • 7.2. Product-Specific Compatibility 6.0.1
      • 7.2.1. RTI Connext Core Libraries
        • 7.2.1.1. Durable Writer History properties prefix must contain “.builtin” substring
        • 7.2.1.2. Durable Writer History properties cannot be set on DomainParticipant
      • 7.2.2. RTI Code Generator
        • 7.2.2.1. Incompatibility issues for Java and .Net when using XCDR2
        • 7.2.2.2. Invalid XSD file from an IDL/XML file if input file contains a range annotation
      • 7.2.3. Security Plugins
        • 7.2.3.1. OpenSSL upgrade
        • 7.2.3.2. Changes to building an application
        • 7.2.3.3. Changes to behavior of intermediate certificates
        • 7.2.3.4. Property key_material_key now required for Secure Persistence Service
        • 7.2.3.5. Issue related to missing keyCertSign when a CA has the KeyUsage X.509 V3 extension
      • 7.2.4. RTI Secure WAN Transport
        • 7.2.4.1. OpenSSL upgrade
        • 7.2.4.2. Changes to building an application
      • 7.2.5. RTI TLS Support
        • 7.2.5.1. OpenSSL upgrade
        • 7.2.5.2. Changes to building an application
  • 8. Upgrading from 5.3.1 to 6.0.0
    • 8.1. General Compatibility 6.0.0
      • 8.1.1. Wire Compatibility
        • 8.1.1.1. RTPS Versions
        • 8.1.1.2. New default GUID generation mode
        • 8.1.1.3. Default shared memory locator has changed
        • 8.1.1.4. 4.2e alignment option deprecated
        • 8.1.1.5. Changed wire representation of TypeObject
        • 8.1.1.6. TypeCode information is not sent by default
      • 8.1.2. Reliability Protocol
        • 8.1.2.1. Changes in behavior of write() operation with KEEP_LAST configuration
      • 8.1.3. Type System Compatibility
        • 8.1.3.1. Migration to Extended CDR encoding version 2 (XCDR2)
        • 8.1.3.2. Changed wire representation of TypeObject
        • 8.1.3.3. TypeCode information is not sent by default
        • 8.1.3.4. Unbounded sequences and strings in XML type representation
        • 8.1.3.5. wchar and wstring language binding changes
        • 8.1.3.6. Properties dds.type_consistency.ignore_member_names and dds.type_consistency.ignore_sequence_bounds have been deprecated
      • 8.1.4. Transport Compatibility
        • 8.1.4.1. Default shared memory locator has changed
        • 8.1.4.2. VxWorks shared-memory transport compatibility
      • 8.1.5. XML Compatibility
        • 8.1.5.1. QoS Profile multiple inheritance
        • 8.1.5.2. XSD issues
      • 8.1.6. Other Compatibility Issues
        • 8.1.6.1. Behavior change when retrieving QoS using topic_name (when there are multiple matching QoSes)
    • 8.2. Product-Specific Compatibility 6.0.0
      • 8.2.1. RTI Connext Core Libraries
        • 8.2.1.1. APIs
        • 8.2.1.2. Generated Code
        • 8.2.1.3. QoS
        • 8.2.1.4. Library Size
        • 8.2.1.5. Memory Consumption
        • 8.2.1.6. Performance
        • 8.2.1.7. RTI Connext Micro Compatibility
      • 8.2.2. Security Plugins
        • 8.2.2.1. Configuration
        • 8.2.2.2. Wire Compatibility
        • 8.2.2.3. APIs
      • 8.2.3. RTI Secure WAN Transport
      • 8.2.4. RTI TLS Support
      • 8.2.5. RTI Ada Language Support
        • 8.2.5.1. APIs
      • 8.2.6. RTI Code Generator
        • 8.2.6.1. Removed -stl Option
        • 8.2.6.2. Removed Support for -notypecode
        • 8.2.6.3. Removed -use42eAlignment
        • 8.2.6.4. Generated code for Extended CDR Encoding Version 2 (XCDR2)
        • 8.2.6.5. Incorrect TypeCode name for member fields whose name was a keyword in Java
        • 8.2.6.6. Modified maximum length of sequences and strings when -unboundedSupport is not used, when converting to XML
        • 8.2.6.7. Traditional C++ compiled with -fno-exceptions
        • 8.2.6.8. Support for new, standard IDL, fixed-width integer types
        • 8.2.6.9. Change in default optimization level for code generation
      • 8.2.7. RTI Connext Micro
        • 8.2.7.1. Connext Compatibility
      • 8.2.8. RTI Routing Service
        • 8.2.8.1. Application Binary Interface
        • 8.2.8.2. APIs
        • 8.2.8.3. Configuration
        • 8.2.8.4. Administration and Monitoring
        • 8.2.8.5. QoS
        • 8.2.8.6. Performance
        • 8.2.8.7. Library Size
        • 8.2.8.8. Documentation
      • 8.2.9. RTI Recording Service
        • 8.2.9.1. APIs
        • 8.2.9.2. Configuration
        • 8.2.9.3. Database Format
        • 8.2.9.4. Running Recording Service 5.3.1
        • 8.2.9.5. Documentation
      • 8.2.10. RTI Persistence Service
        • 8.2.10.1. External Database Compatibility
        • 8.2.10.2. Persistent Storage (Database) Format Compatibility
        • 8.2.10.3. Persistence Storage (Database) Locking Compatibility
        • 8.2.10.4. Dynamically Linked Libraries
      • 8.2.11. RTI Database Integration Service
        • 8.2.11.1. Database Compatibility
      • 8.2.12. RTI Cloud Discovery Service
      • 8.2.13. RTI Launcher
        • 8.2.13.1. Configuration
      • 8.2.14. RTI Administration Console
        • 8.2.14.1. New Default GUID Generator Mode
        • 8.2.14.2. New GTK+ and Cairo Dependencies
        • 8.2.14.3. Connext Micro Compatibility
      • 8.2.15. RTI Monitor
      • 8.2.16. RTI Utilities
        • 8.2.16.1. Dynamically Linked Libraries
  • 9. Regressions
    • 9.1. Regressions in 7.7 LTS
      • 9.1.1. Intraparticipant communication fails when origin authentication is applied to messages
      • 9.1.2. Segmentation fault when origin authentication is applied to submessages only
      • 9.1.3. No endpoint discovery when using Lightweight Security and TypeObject v2
      • 9.1.4. Instance state consistency fails after reconnection in secure systems with key revisions enabled
    • 9.2. Regressions in 7.3 LTS
      • 9.2.1. General
        • 9.2.1.1. Running scripts under $NDDSHOME/bin creates two processes
      • 9.2.2. Core Libraries
        • 9.2.2.1. Duplicate network traffic captures when creating WaitSets, AsyncWaitSets, or GuardConditions
        • 9.2.2.2. Error when setting QoS on Publisher or Subscriber without endpoints
        • 9.2.2.3. Crash on DDS_DomainParticipantFactory_finalize_instance when using XML-Based Application Creation
        • 9.2.2.4. Unexpected error messages when disposing of an instance while using batching and setting serialize_key_with_dispose to TRUE
        • 9.2.2.5. RTI DDS Spy shows DDS_DataReader_get_matched_publication_participant_data error before leaking memory
        • 9.2.2.6. Misleading warning message when one non-loopback interface doesn’t support multicast
        • 9.2.2.7. Incorrect timestamp in log messages with microseconds higher than 500000
        • 9.2.2.8. Vulnerability: Potential invalid read memory access in Connext applications when subscribing to PublicationBuiltinTopicData
        • 9.2.2.9. Incorrect value of an infinite duration in non-Java APIs
        • 9.2.2.10. Possible unbounded memory growth on DataReader of keyed type after failing to match with a remote DataWriter
        • 9.2.2.11. Possible crash when creating DomainParticipants concurrently
        • 9.2.2.12. Memory leaks and errors when using DynamicDataReaders or FlatData DataReaders plus DDS-fragmentation and compression or encryption
        • 9.2.2.13. Some properties no longer accept LENGTH_UNLIMITED string as valid value
        • 9.2.2.14. Possible segmentation fault while enabling a DataWriter that enables batching
        • 9.2.2.15. Running out of memory during DomainParticipant creation causes DomainParticipantFactory finalization to hang
        • 9.2.2.16. Unexpected warning during DomainParticipant enablement when locator reachability enabled
      • 9.2.3. Code Generator
        • 9.2.3.1. Code generation fails if @verbatim annotation encountered
        • 9.2.3.2. Using //@resolve-name false does not avoid resolution when a constant is used as a size for an array, sequence bound, string bound, or wstring bound
      • 9.2.4. Admin Console
        • 9.2.4.1. Discovery peer changes not consistently applied or maintained
      • 9.2.5. Security Plugins
        • 9.2.5.1. Potential stack buffer read overflow in Builtin Security Plugins when registering local endpoint
        • 9.2.5.2. Potential segmentation fault in Builtin Security Plugins when discovering a DomainParticipant
        • 9.2.5.3. Segmentation fault in Java while enabling a DataWriter that protects payloads and enables batching
      • 9.2.6. Routing Service
        • 9.2.6.1. Unexpected error messages when Routing Service disposes of an instance while using batching and setting serialize_key_with_dispose to TRUE
    • 9.3. Regressions in 6.1 LTS
      • 9.3.1. Introduced in 6.1.1/6.1.2
        • 9.3.1.1. Core Libraries
        • 9.3.1.2. Security Plugins
        • 9.3.1.3. Persistence Service
        • 9.3.1.4. Limited Bandwidth Plugins
      • 9.3.2. Introduced in 6.1.0
        • 9.3.2.1. Core Libraries
        • 9.3.2.2. Code Generator
        • 9.3.2.3. Admin Console
        • 9.3.2.4. TLS Support
        • 9.3.2.5. Security Plugins
        • 9.3.2.6. Routing Service
        • 9.3.2.7. Recording Service
        • 9.3.2.8. Cloud Discovery Service
    • 9.4. Regressions in 6.0 LTS
      • 9.4.1. Introduced in 6.0.0
        • 9.4.1.1. Core Libraries
        • 9.4.1.2. Security Plugins
        • 9.4.1.3. Code Generator
        • 9.4.1.4. Persistence Service
        • 9.4.1.5. Routing Service
        • 9.4.1.6. Recording Service
        • 9.4.1.7. Cloud Discovery Service
        • 9.4.1.8. Queuing Service
      • 9.4.2. Introduced in 6.0.1
        • 9.4.2.1. Core Libraries
        • 9.4.2.2. Routing Service
        • 9.4.2.3. Recording Service
        • 9.4.2.4. Prototyper
        • 9.4.2.5. Security Plugins
  • 10. Changes to This Document
  • Copyrights and Notices
RTI Connext Migration Guide
  • 3. Upgrading from 7.3.0 to 7.3.1

3. Upgrading from 7.3.0 to 7.3.1

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

The following sections describe how to upgrade from Connext 7.3.0 to Connext 7.3.1.

  • 3.1. General Compatibility 7.3.1
    • 3.1.1. Wire Compatibility
      • 3.1.1.1. RTPS Versions
      • 3.1.1.2. New requirement if you interoperate with DDS vendors that produce multiple RTPS messages in a single datagram
  • 3.2. Product-Specific Compatibility 7.3.1
    • 3.2.1. RTI Connext Core Libraries
      • 3.2.1.1. socket_monitoring_kind default changed to POLL
    • 3.2.2. RTI Security Plugins
      • 3.2.2.1. Changes to Building an Application
      • 3.2.2.2. Configuration Changes
      • 3.2.2.3. Security Plugins SDK
    • 3.2.3. RTI Infrastructure Services
      • 3.2.3.1. Persistence Service
      • 3.2.3.2. Web Integration Service
    • 3.2.4. RTI TLS Support
      • 3.2.4.1. OpenSSL 3 upgrade
    • 3.2.5. RTI Connext Observability Framework
      • 3.2.5.1. Disallow unrealistic values of polling_period
Previous Next

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

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

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