RTI Core Libraries and Utilities

Why DataWriter::write() execution time can grow with local multicast subscribers

Summary On Linux/Windows and potentially other operating systems, when a DataWriter sends data samples to a multicast address, the performance of the underlying UDP sendmsg() call varies depending on whether multicast DataReaders are located on the same local host. If there are no local, multicast ...
grayson
Fri, 08/01/2025 - 15:51
152 reads — 0 comments

XTypes compliance mismatch

By default, Connext data serialization is not fully compliant with Extended CDR encoding. While this doesn't affect correctness it may prevent interoperability with other vendors. To make Connext compatible with the OMG 'Extensible and Dynamic Topic Types for DDS' specification, version 1.3 , you ...
arobles
Thu, 06/12/2025 - 07:43
315 reads — 0 comments

How do I restrict and prioritize interfaces for RTI Connext to use?

(This article expands on the community post: How do I restrict RTI Connext to use only a subset of interfaces? ) On a machine with multiple NICs, users can restrict RTI Connext® traffic to a subset of the available network interfaces (NICs). RTI’s Connext DDS 7.3 introduced the capability to ...
mmohr
Tue, 12/17/2024 - 10:00
1835 reads — 0 comments

Why do I see the WARNING message “PRESCstReaderCollator_getKey:instance not found”?

When processing a metadata sample that indicates the instance transition change to NOT_ALIVE_NO_WRITERS or NOT_ALIVE_DISPOSED, you may see the following WARNING messages when calling the get_key_value API: WARNING PRESCstReaderCollator_getKey:instance not found WARNING PRESPsReader_getKey:!collator ...
afernandez
Tue, 12/17/2024 - 07:10
732 reads — 0 comments

Why do I get an OSSL_STORE API error and crash when creating a secure participant on Linux?

On Linux systems, if you are creating a DomainParticipant with Security Plugins enabled, and your application is linked to both TensorFlow and OpenSSL , you may see errors like this: RTI_Security_Util_uriToStringOssl:OpenSSL function PEM_write_bio_X509 failed with error: error:0c00009b:ASN.1 ...
grayson
Tue, 11/12/2024 - 10:05
977 reads — 0 comments

High CPU usage after SHMEM resources are removed by a third-party

The shared memory built-in transport in RTI Connext uses IPC segments and semaphores under the hood to perform DDS communication between DomainParticipants. It is important that those IPC resources are not destroyed while RTI Connext applications are using them. Failure to do so may result in ...
scardenete
Wed, 02/14/2024 - 08:41
2311 reads — 0 comments

Achieving low-jitter performance with Connext Pro

Achieving low jitter and more deterministic write times and real-time performance requires in-depth tuning at the OS layer and DDS layer. It tends to involve a long list of recommendations to apply e.g. you can see advice online that involves similar checklists. This article summarizes best practices, and we recommend exploring and testing all the recommendations listed here. ...
grayson
Wed, 11/22/2023 - 06:39
17985 reads — 0 comments

Why do I get 'User storage is not valid' error when I create a DDS Entity

The multiple APIs of Connext have an internal concept named User Storage, which is used to store API-specific data required for certain features. This concept is normally part of the DomainParticipant entities and is configured through code as a QoS. While the APIs will configure this concept ...
anunez
Fri, 10/20/2023 - 01:18
10450 reads — 0 comments

Enabling communication between SPDP and SPDP2 participants with Routing Service

Communication between participants using Simple Participant Discovery Protocol (SPDP) and Simple Participant Discovery Protocol 2.0 (SPDP2) is not possible by default. Both participant and endpoint discovery will fail to complete between an SPDP and SPDP2 participant. See Discovery Overview in the ...
olivia.dorencz
Mon, 02/06/2023 - 14:35
35361 reads — 0 comments

Which RTI library architecture should I use for my Linux platform?

To determine if your Linux platform is compatible with an RTI architecture, you will need to know the CPU architecture (e.g. x64 or ARM), GLIBC, and GLIBCXX versions in your target platform. To find the GLIBC library, here are the steps we recommend you run on your target platform: $ ldd `which ls ...
grayson
Wed, 02/01/2023 - 16:49
2748 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities