5. What’s Fixed in 7.3.0 LTS

This section describes bugs fixed in Connext 7.3.0 LTS. These are fixes since 7.2.0. For information on what was fixed in releases 7.0.0, 7.1.0, and 7.2.0, which are all also part of 7.3.0 LTS, see Previous Releases.

[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.

• 5.1. Discovery
  • 5.1.1. [Critical] SPDP2 participants with RTPS peers and participant_liveliness_assert_period less than participant_announcement_period may have crashed upon deletion *
  • 5.1.2. [Major] Rediscovery failed if participant with SPDP2 lost liveliness before receiving remote participant’s configuration message *
  • 5.1.3. [Major] Participants with SPDP2 failed to discover new participant that was using the same unicast locator as a previously discovered (and not removed) participant *
• 5.2. Serialization and Deserialization
  • 5.2.1. [Critical] Endpoint creation failed for types with large maximum serialized size
• 5.3. Usability
  • 5.3.1. [Major] Incorrect, too-restrictive maximum string size enforced on certain XML fields
  • 5.3.2. [Major] rtipkginstaller error in Windows when user name had space *
• 5.4. Transports
  • 5.4.1. [Critical] High CPU and several warnings in some cases when using MultiChannel or TransportUnicast QoS
  • 5.4.2. [Critical] Participant may have received RTPS traffic over SHMEM transport not intended for participant
  • 5.4.3. [Critical] Undefined behavior of shared memory transport if shared mutex or semaphores removed externally
  • 5.4.4. [Minor] DLL leak when using UDP/TCP transports
• 5.5. Reliability Protocol and Wire Representation
  • 5.5.1. [Critical] Writer-side filtered samples not marked as acknowledged when application acknowledgement was used
• 5.6. Debuggability
  • 5.6.1. [Major] Thread names longer than 15 characters on QNX platforms caused errors in API calls
  • 5.6.2. [Major] Wrong information in shared memory ‘send’ error log message
  • 5.6.3. [Minor] take_discovery_snapshot APIs incorrectly always printed keyed_type as false *
• 5.7. Content Filters and Query Conditions
  • 5.7.1. [Critical] Error message printed for each filtered sample when using writer-side filtering, FlatData, and Zero Copy over shared memory *
• 5.8. TopicQueries
  • 5.8.1. [Critical] Communication could stop when using bounded max_samples and TopicQueries
  • 5.8.2. [Major] max_samples resource limit not honored in some cases when using an unkeyed topic and TopicQueries
• 5.9. Logging
  • 5.9.1. [Major] Modern C++ Distributed Logger Options header incorrectly included generated header file *
  • 5.9.2. [Major] Misleading log message when sending specific number of bytes through socket *
  • 5.9.3. [Major] Missing logging on the standard output for Windows GUI applications
  • 5.9.4. [Minor] Incorrect error message when setting inconsistent ReaderDataLifeCycleQosPolicy values
  • 5.9.5. [Minor] Log messages truncated below maximum size of 1024 bytes *
  • 5.9.6. [Trivial] Error message that was printed when failing to allocate the writer buffer pool was wrong *
  • 5.9.7. [Trivial] Missing space between Activity Context and message text if Logging Category was printed *
• 5.10. Dynamic Data
  • 5.10.1. [Major] DynamicData equals operation returned incorrect results for sequences of different lengths
• 5.11. APIs (C or Traditional C++)
  • 5.11.1. [Critical] Traditional C++ get_participants() API returned invalid pointer if Monitoring Library 2.0 was enabled
  • 5.11.2. [Major] Potential error when waiting for samples in C API
• 5.12. APIs (Modern C++ API)
  • 5.12.1. [Major] Potential crash when mixing the C and Modern C++ APIs in the same executable
  • 5.12.2. [Major] DataReader created with builtin topic not automatically destroyed *
  • 5.12.3. [Major] Possible link error when building a Windows DLL *
  • 5.12.4. [Minor] Conversion of invalid Time to integer units caused unexpected behavior
• 5.13. APIs (Java)
  • 5.13.1. [Major] DynamicData API now supports setting and getting wchar fields
  • 5.13.2. [Major] Possible data serialization error for keyed DataReaders using XCDR2 format
  • 5.13.3. [Minor] “data_to_string” of DynamicDataTypeSupport failed with exception
• 5.14. APIs (Python)
  • 5.14.1. [Critical] Potential deadlock in applications that call certain APIs and use Entity Listeners
  • 5.14.2. [Minor] Possible memory leak in DynamicData.loan_value
  • 5.14.3. [Minor] Converting a SampleInfo object to string failed when source_timestamp was invalid
  • 5.14.4. [Minor] Some functions didn’t allow keyword arguments
• 5.15. APIs (Multiple Languages)
  • 5.15.1. [Major] Using a Listener and a Waitset in the same application may have resulted in the Waitset waking up unexpectedly
  • 5.15.2. [Major] Sentinel constant for “invalid” Time contained unexpected value *
  • 5.15.3. [Minor] IDL printing of Enum TypeCodes was not standards-compliant
  • 5.15.4. [Minor] Extensibility of unions defined within modules incorrectly printed as IDL *
  • 5.15.5. [Minor] Incorrect output when printing a union with an enum discriminator as IDL
  • 5.15.6. [Trivial] First enum label not printed
• 5.16. XML Configuration
  • 5.16.1. [Critical] Potential segmentation fault when using XML application creation if the names of <domain_participant_library> and <domain_library> were the same
  • 5.16.2. [Major] Micro Compatibility Builtin Profiles updated UDPv4 message_size_max so that samples larger than 8192 were not silently dropped by Micro applications
  • 5.16.3. [Minor] XML parser did not parse scientific notation
• 5.17. Instances
  • 5.17.1. [Critical] Two log messages used memory after it was freed *
  • 5.17.2. [Major] Instance state consistency may not have worked for DataReaders using multiple data representations *
  • 5.17.3. [Major] Indeterminate instance state in systems with multiple DataWriters *
• 5.18. Crashes
  • 5.18.1. [Critical] Crash when deserializing PID_TYPE_OBJECT_LB with class ID of RTI_OSAPI_COMPRESSION_CLASS_ID_NONE
  • 5.18.2. [Critical] Potential crash while calling DynamicData APIs when running out of system memory
  • 5.18.3. [Critical] Potential crash when calling DDS_TypeCodeFactory_create_value_tc_ex with a NULL ex parameter
  • 5.18.4. [Critical] Crash when calling DDS_DataWriter_set_qos with a NULL qos parameter
  • 5.18.5. [Critical] Crash when performing an illegal call to DDS_DataWriter_get_qos
  • 5.18.6. [Critical] Crash if SPDP2 participant received unexpected field in participant discovery message *
  • 5.18.7. [Critical] Crash during DomainParticipant initialization if failure to get local address mapping when using UDPV4_WAN transport
  • 5.18.8. [Critical] Crash when converting a DynamicData object to a CDR buffer
  • 5.18.9. [Critical] Potential crash if allocation of RTI Monitoring Library’s publish thread failed
  • 5.18.10. [Critical] Segmentation fault upon destruction of DDSGuardCondition or DDSWaitset
  • 5.18.11. [Critical] Crash if participant received endpoint discovery sample and was not able to allocate memory to process it
  • 5.18.12. [Critical] Possible exception after using a Condition object if it was not explicitly disposed
  • 5.18.13. [Critical] Potential crash or errors when using SHMEM transport in QNX *
  • 5.18.14. [Critical] Crash if participant failed to allocate memory for endpoint discovery type plugins
  • 5.18.15. [Critical] Modern C++ Distributed Logger may hang or crash upon instance finalization *
  • 5.18.16. [Critical] Invalid multicast locator could cause precondition error or segmentation violation
  • 5.18.17. [Critical] Crash during DomainParticipant enable operation when running out of system memory
  • 5.18.18. [Critical] Segmentation fault when a reader was deleted while a remote writer cleanup event was scheduled *
  • 5.18.19. [Critical] Race condition between the creation of a Replier and the call to its Listener
  • 5.18.20. [Critical] Undefined behavior when Requesters or Repliers for same service name were concurrently created and deleted
  • 5.18.21. [Critical] Hang led to crash if Monitoring Library 2.0 was enabled then right away disabled *
  • 5.18.22. [Critical] Possible crash when creation of TCP Transport failed
  • 5.18.23. [Critical] Possible crash upon destruction of TCP transport if it was created programmatically and it logged messages
• 5.19. Hangs
  • 5.19.1. [Critical] Undefined behavior when using SHMEM transport in Linux, macOS, QNX, INTEGRITY, and LynxOS
  • 5.19.2. [Major] Possible deadlock related to failures in DNS Tracker
  • 5.19.3. [Critical] Segmentation fault or hang when using SHMEM transport on VxWorks 6 or higher platforms
• 5.20. Memory Leaks/Growth
  • 5.20.1. [Critical] Memory leak in best-effort writers when switching from more than one unicast locator to a multicast locator
  • 5.20.2. [Critical] Concurrency problem in Asynchronous WaitSet’s global instance initialization led to memory and TSS key leaks in multi-threading scenarios
  • 5.20.3. [Critical] Memory leak when creating a QueryCondition with Parameters
  • 5.20.4. [Critical] Memory leak when using NetworkCaptureParams
  • 5.20.5. [Critical] Memory Leak in Java API when printing QoS objects
  • 5.20.6. [Critical] Asynchronous WaitSet global instance’s thread-specific storage key leaked
  • 5.20.7. [Major] Memory leak when using XML-Based Application Creation and DynamicData
  • 5.20.8. [Minor] Memory leak when finalizing DomainParticipantFactory for first time
  • 5.20.9. [Minor] DomainParticipantFactory was leaked when factory finalization failed
  • 5.20.10. [Minor] Potential Memory leak upon ContentFilteredTopic creation failure
  • 5.20.11. [Critical] ODBC DataWriters may have leaked instances when they were replaced if writer-side filtering was used
• 5.21. Data Corruption
  • 5.21.1. [Critical] Undefined behavior using XCDR2 with keyed topic types with key union members
  • 5.21.2. [Critical] Stack overflow if value of “rti.monitor.config.publish_thread_options” property had 512 or more characters
  • 5.21.3. [Critical] Failure to send serialized key with dispose when using dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size property
  • 5.21.4. [Critical] Error uncompressing samples when using batching and setting serialize_key_with_dispose to TRUE
  • 5.21.5. [Critical] SampleInfo’s flag and related_original_publication_virtual_guid may have had invalid information for unkeyed Topics
  • 5.21.6. [Critical] DataReader on a Topic using an appendable type may have received samples with incorrect value
• 5.22. OMG Specification Compliance
  • 5.22.1. [Critical] Extensible types did not include padding size in length value of each element of RTPS parameter list
  • 5.22.2. [Critical] Problems exchanging data with other vendors for types containing unbounded members
  • 5.22.3. [Critical] Non-primitive sequences and arrays serialized incorrectly with XCDR2_DATA_REPRESENTATION when using dds.type_plugin.dheader_in_non_primitive_collections
  • 5.22.4. [Critical] DataReader on a Topic using an appendable type may have received samples with incorrect value
  • 5.22.5. [Major] FlatData did not support XCDR2-compliant serialization
• 5.23. Entities
  • 5.23.1. [Critical] FlatData language binding allowed you to specify XCDR data representation
• 5.24. Interoperability
  • 5.24.1. [Minor] JRE version check prevented desktop Java tools from opening
• 5.25. Other
  • 5.25.1. [Critical] Potential bus error when calling print and to_string APIs in TypeCode *
  • 5.25.2. [Critical] Restarted keyed DataReaders using durable reader state and destination order by source timestamp may have received old samples
  • 5.25.3. [Critical] Reliable DataReader may have stopped receiving samples from DataWriter using durable writer history and DDS fragmentation
  • 5.25.4. [Critical] Support for systems running beyond 2038 when using a database and logging
  • 5.25.5. [Major] Durable writer history failed to restore data in buildable sources
  • 5.25.6. [Minor] Discovery plugins libraries did not close if creation of plugin failed
  • 5.25.7. [Trivial] Strings with default size (255) may have printed as unbounded when printing TypeCodes as IDL
  • 5.25.8. [Trivial] Alias’s annotations may not have printed out correctly

* This bug does not affect you if you are upgrading from 6.1.x or earlier.