3.2. Product-Specific Compatibility 7.3.0

After addressing migration issues in Section 3.1, address Core Libraries issues in Section 3.2.1. Then review and address the rest of the product-specific migration issues in this section for release 7.3.0.

• 3.2.1. RTI Connext Core Libraries
  • 3.2.1.1. Deprecations or Removals
    • 3.2.1.1.1. Durable writer history, durable reader state, and Persistence Service no longer support external databases
  • 3.2.1.2. API Compatibility
    • 3.2.1.2.1. Memory leak when using coherent sets and the Copy Take/Read APIs in C
    • 3.2.1.2.2. Migrating from Connector to the Connext Python API
    • 3.2.1.2.3. Year 2038 support
    • 3.2.1.2.4. Constant rti::core::policy::ReceiverPool::LENGTH_AUTO has been replaced
  • 3.2.1.3. Configuration Changes
    • 3.2.1.3.1. Communication with earlier releases when using DomainParticipant partitions
    • 3.2.1.3.2. DDS_TransportMulticastQosPolicy will now fail if using TCP or TLS as transports
    • 3.2.1.3.3. Error for max_app_ack_response_length longer than 32kB
    • 3.2.1.3.4. Potential unexpected delay in receiving samples due to randomization of sample sent time between min and max response delays
    • 3.2.1.3.5. DataWriters no longer match DataReaders that request inline QoS
    • 3.2.1.3.6. Reduced number of participant announcements at startup
    • 3.2.1.3.7. Enhanced validation for FlatData language binding in QoS settings for C++ APIs
    • 3.2.1.3.8. MonitoringLoggingForwardingSettings security_forwarding_level renamed security_event_forwarding_level
  • 3.2.1.4. Logging Changes
    • 3.2.1.4.1. SECURITY Syslog facility meaning and name have changed
    • 3.2.1.4.2. LogMessage is_security_message meaning has changed
    • 3.2.1.4.3. Logging category names changed in Activity Context
  • 3.2.1.5. Library Size
  • 3.2.1.6. Memory Consumption
    • 3.2.1.6.1. General Memory Consumption
    • 3.2.1.6.2. Increased availability of instance key values may result in higher memory usage
  • 3.2.1.7. Network Performance
  • 3.2.1.8. Discovery Performance
    • 3.2.1.8.1. Simple Participant Discovery: reduced bandwidth usage may delay discovery time
  • 3.2.1.9. Transport Compatibility
    • 3.2.1.9.1. Communication with QNX applications in previous releases no longer possible when using shared-memory transport
  • 3.2.1.10. Other Changes
    • 3.2.1.10.1. Reduction in maximum number of Publishers and Subscribers per DomainParticipant
• 3.2.2. Security Plugins
  • 3.2.2.1. Deprecations or Removals
    • 3.2.2.1.1. HMAC-Only Mode Deprecation
  • 3.2.2.2. API Compatibility
    • 3.2.2.2.1. Removed check_remote_topic
  • 3.2.2.3. Changes to Building an Application
    • 3.2.2.3.1. Link against both libssl and libcrypto
    • 3.2.2.3.2. OpenSSL 3.0 upgrade and 1.1.1 removal
    • 3.2.2.3.3. wolfSSL upgrade
    • 3.2.2.3.4. wolfSSL build flags
    • 3.2.2.3.5. Security Plugins SDK no longer uses cmocka
    • 3.2.2.3.6. Degradation of Security Plugins performance when switching from OpenSSL 1.1.1 to OpenSSL 3.0
  • 3.2.2.4. Changes to Shipped Examples
    • 3.2.2.4.1. Updated shipped examples to support different cryptographic libraries
  • 3.2.2.5. Configuration Changes
    • 3.2.2.5.1. Removed support for DSA
    • 3.2.2.5.2. Enforcement of supported Digital Signature algorithms now supported in Connext
    • 3.2.2.5.3. Deprecated properties in favor of pre-shared key (PSK) protection
    • 3.2.2.5.4. Year 2038 support: DDS:Security:LogTopic replaced with DDS:Security:LogTopicV2
    • 3.2.2.5.5. Deprecation of the dds.data_writer.history.use_530_encoding_alignment property
    • 3.2.2.5.6. Deprecation of the cryptography.encryption_algorithm property
  • 3.2.2.6. Logging Changes
    • 3.2.2.6.1. Changed fields in Security Events log messages
  • 3.2.2.7. Performance and Scalability
    • 3.2.2.7.1. Scalability is slightly affected in systems with more than 900 matching DomainParticipants
  • 3.2.2.8. Wire Compatibility
    • 3.2.2.8.1. Batching of protected data is not backwards compatible
    • 3.2.2.8.2. Data protection kind did not protect serialized keys sent with dispose samples
    • 3.2.2.8.3. AES-192 is not supported when communicating with earlier releases
    • 3.2.2.8.4. Deprecated property values for configuring the symmetric cipher algorithm
• 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.2.1. <refresh_period> tag removed and replaced by new tags to configure announcement resends
    • 3.2.4.2.2. domain_id_info_seq field in DatabasePeriodic type used in monitoring removed
  • 3.2.4.3. Persistence Service
    • 3.2.4.3.1. Durable writer history, durable reader state, and Persistence Service no longer support external databases
    • 3.2.4.3.2. Incompatible persistent storage (database) format
    • 3.2.4.3.3. Default journal_mode and synchronization values have changed
    • 3.2.4.3.4. Web Integration Service no longer installed in separate package
• 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.1.1. Removed wrong QoS elements from QoS policies
    • 3.2.6.1.2. Changes in valid ranges of QoS elements to align with API
  • 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