RTI Connext Migration Guide
6.0.0
1. Upgrade Overview
2. General Compatibility
2.1. Platforms
2.2. Wire Compatibility
2.2.1. New default GUID generation mode
2.2.2. Default shared memory locator has changed
2.2.3. 4.2e alignment option deprecated
2.2.4. Changed wire representation of TypeObject
2.2.5. TypeCode information is not sent by default
2.3. Reliability Protocol
2.3.1. Changes in behavior of write() operation with KEEP_LAST configuration
2.4. Type System Compatibility
2.4.1. Migration to Extended CDR encoding version 2 (XCDR2)
2.4.1.1. Overview
2.4.1.2. Known Issues
2.4.2. Changed wire representation of TypeObject
2.4.3. TypeCode information is not sent by default
2.4.4. Unbounded sequences and strings in XML type representation
2.4.5. wchar and wstring language binding changes
2.4.6. Properties dds.type_consistency.ignore_member_names and dds.type_consistency.ignore_sequence_bounds have been deprecated
2.5. Transport Compatibility
2.5.1. Default shared memory locator has changed
2.5.2. VxWorks shared-memory transport compatibility
2.6. XML Compatibility
2.6.1. QoS Profile multiple inheritance
2.6.2. XSD issues
2.7. Other Compatibility Issues
2.7.1. Behavior change when retrieving QoS using topic_name (when there are multiple matching QoSes)
3. Product-Specific Compatibility
3.1. RTI Connext DDS Core Libraries
3.1.1. Application Binary Interface
3.1.2. APIs
3.1.2.1. Wchar and wstring language binding changes
3.1.2.2. Dynamic Data compatibility issues
3.1.3. Generated Code
3.1.3.1. Generated code compatibility
3.1.3.2. Changed modern C++ default IDL mapping
3.1.4. QoS
3.1.4.1. Properties dds.type_consistency.ignore_member_names and dds.type_consistency.ignore_sequence_bounds have been deprecated
3.1.5. Library Size
3.1.6. Memory Consumption
3.1.7. Performance
3.1.8. RTI Connext DDS Micro Compatibility
3.2. RTI Security Plugins
3.2.1. Configuration
3.2.1.1. Changed Authentication and Access Control property names
3.2.1.2. Changed default Persistence Service “dds.data_writer.history.key_material_key”
3.2.1.3. Changed Persistence Service encryption algorithm
3.2.1.4. Changed matching behavior of allowed partitions condition
3.2.1.5. Change to mutability of Publisher PartitionQosPolicy
3.2.1.6. New protection for Builtin Logging Topic
3.2.2. Wire Compatibility
3.2.2.1. Participants and endpoints using inconsistent security configuration do not communicate
3.2.3. APIs
3.2.3.1. Changes in DDS types and definitions
3.2.3.2. Changes in APIs
3.2.3.3. get_datawriter_sec_attributes and get_datareader_sec_attributes must support receiving builtin topic names
3.3. RTI Secure WAN Transport
3.4. RTI TLS Support
3.5. RTI Ada Language Support
3.5.1. APIs
3.5.1.1. Write_W_Params requires its DDS.WriteParams_T argument to be modifiable
3.5.1.2. Wide character representation change
3.6. RTI Code Generator
3.6.1. Removed -stl Option
3.6.2. Removed Support for -notypecode
3.6.3. Removed -use42eAlignment
3.6.4. Generated code for Extended CDR Encoding Version 2 (XCDR2)
3.6.5. Incorrect TypeCode name for member fields whose name was a keyword in Java
3.6.6. Modified maximum length of sequences and strings when -unboundedSupport is not used, when converting to XML
3.6.7. Traditional C++ compiled with -fno-exceptions
3.6.8. Support for new, standard IDL, fixed-width integer types
3.6.9. Change in default optimization level for code generation
3.7. RTI Connext DDS Micro
3.7.1. New Installation Procedure
3.7.2. Change In Documentation
3.7.3. Application Binary Interface
3.7.4. APIs
3.7.4.1. Wchar and wstring language binding changes
3.7.4.2. RTI_CERT compilation flag not supported in this release
3.7.4.3. Generated code compatibility
3.7.4.4. Default UDP socket buffer size on QNX changed to 64KB
3.7.5. Connext DDS Compatibility
3.8. RTI Routing Service
3.8.1. Application Binary Interface
3.8.1.1. Service Library
3.8.1.2. Infrastructure Library
3.8.2. APIs
3.8.2.1. Adapter API
3.8.2.2. Service API
3.8.3. Configuration
3.8.3.1. XSD compatibility
3.8.3.2. XML Validation
3.8.4. Administration and Monitoring
3.8.4.1. New models
3.8.4.2. “Ignore” warnings
3.8.5. QoS
3.8.6. Performance
3.8.7. Library Size
3.8.8. Documentation
3.9. RTI Recording Service
3.9.1. APIs
3.9.2. Configuration
3.9.3. Database Format
3.9.3.1. How to Convert a Legacy Database
3.9.3.2. How to Replay a Legacy Database
3.9.4. Running Recording Service 5.3.1
3.9.5. Documentation
3.10. RTI Persistence Service
3.10.1. External Database Compatibility
3.10.2. Persistent Storage (Database) Format Compatibility
3.10.3. Persistence Storage (Database) Locking Compatibility
3.10.4. Dynamically Linked Libraries
3.11. RTI Database Integration Service
3.11.1. Database Compatibility
3.12. RTI Cloud Discovery Service
3.13. RTI Launcher
3.13.1. Configuration
3.13.1.1. Custom buttons
3.13.1.2. New GTK+ dependency
3.14. RTI Administration Console
3.14.1. New Default GUID Generator Mode
3.14.2. New GTK+ and Cairo Dependencies
3.14.3. Connext DDS Micro Compatibility
3.15. RTI Monitor
3.16. RTI Utilities
3.16.1. Dynamically Linked Libraries
4. Regressions
4.1. RTI Connext DDS Core Libraries
4.1.1. XSD issues
4.1.1.1. Order enforced in <domain_participant> tag
4.1.1.2. Order enforced in <publisher> tag
4.1.1.3. XSD validation fails if topic_ref or register_type_ref uses some non-alphanumeric characters
4.1.2. Dynamic Data issues
4.1.2.1. Segmentation fault when using unkeyed DynamicData
DataReader
with content filter and writer-side filtering
4.1.2.2. Invalid serialization of samples with types containing primitive members that require padding
4.1.2.3. Possible data corruption or crash when using DynamicData and a type with inheritance
4.1.3. Discovery does not complete, and there is no error
4.1.4. Crash when deserialized_type_object_dynamic_allocation_threshold set to 0
4.1.5. Wrong return code for DDS::DataWriter::get_matched_subscription_data and DDS::DataReader::get_matched_publication_data
4.1.6. DataReader reports incorrect sample lost and rejected when receiving coherent set
4.1.7. QoS policies not resolved to correct values
4.2. RTI Security Plugins
4.2.1. Possible lack of SUBSCRIPTION_MATCHED_STATUS if a DataWriter loses liveliness with the DataReader
4.2.2.
DataWriter
does not report PUBLICATION_MATCHED_STATUS for
DataReaders
that are inactive when it receives their key material
4.3. RTI Code Generator
4.3.1. Invalid serialization of samples with types containing primitive members that require padding
4.3.2. Java exception during serialization/deserialization of keyed types whose key is an unkeyed nested type with unbounded members
4.3.3. Incorrect deserialization in .Net of samples from certain types when published from a writer with disable_inline_keyhash set to true
4.3.4. Generated code in traditional C++ with namespaces for an IDL containing a nested module called “rti” will not compile
4.4. RTI Routing Service
4.4.1. Create method in Service API fails to parse XML snippets that start with ‘str://’
4.4.2. Executable ignores logging QoS
4.4.3. User-defined DTD entities no longer supported
4.5. RTI Recording Service
4.5.1. Legacy deserialized database table cannot be replayed or converted if it contains compact byte sequences or arrays
4.5.2. Segmentation fault in
Replay Service
or
Converter
if recorded topics have “::” in their names
4.6. RTI Cloud Discovery Service
5. Changes to This Document
6. Copyrights
RTI Connext Migration Guide
Docs
»
3. Product-Specific Compatibility
»
3.12. RTI Cloud Discovery Service
View page source
3.12. RTI Cloud Discovery Service
¶
See
Section 4.6
for regressions related to
Cloud Discovery Service
in release 6.0.0.