RTI Core Libraries and Utilities

The identity certificates that were shipped with Connext 5.3.1 expired on February 16th, 2019. Therefore, creating a DomainParticipant that tries to use those certificates will fail and will report different problems. This solution documents the most common error messages and provides a set of new certificates, private keys, signed governance, and signed permissions documents valid through February 2029. ...
4581 reads — 0 comments
Connext 6 introduces two features: Zero Copy Transfer over Shared Memory and FlatData Language Binding . These features enable the middleware to reduce the number of copies involved in sending a sample, resulting in lower latencies for large data. The following examples show how to use these ...
60862 reads — 0 comments
The DDS reliability protocol uses Heartbeat messages and ACKNACK messages to ensure the receipt of data. A DataReader sends an ACKNACK message in response to a DataWriter’s Heartbeat; this ACKNACK message indicates which samples the reader received, and which samples it has yet to receive. For ...
8499 reads — 0 comments
Endpoint Discovery uses either unicast or multicast, depending on the situation. First, some background: Endpoint Discovery is the process used by endpoints (that is, DataReaders and DataWriters ) to locate each other before they can begin to communicate user data. When a DomainParticipant is ...
8670 reads — 0 comments
The following message is an internal debugging message that is printed at REMOTE verbosity level: COMMENDSrWriterService_onSubmessage:!ACK ignored: number of active RR is > 1, but sum of RR at is 0 Seeing this message is expected during normal operation and it does not indicate that something is ...
4138 reads — 0 comments
When enabling RTI Monitoring library via the QoS file, a Connext DDS application might report a memory leak when using valgrind for memory usage analysis. An example of the valgrind output for this memory leak is found at the end of this article. Please see this Knowledge Base article for more ...
4562 reads — 0 comments
Note : Applies to RTI Connext 5.2.x and above. When you run an RTI Connext DDS host installer, the installation directory will always be like this: <default install path or user defined installation path>/rti_connext_dds-x.x.x . The installer itself adds the “ rti_connext_dds-x.x.x ”. If you ...
3330 reads — 0 comments
QoS configurations for transport when starting applications with network interfaces disabled for IP mobility use case With the introduction of version 5.3.0, Connext DDS supports Locator change at runtime. The IP mobility feature allows DDS applications to start without enabled network interfaces. ...
8817 reads — 0 comments
RTI Connext DDS assigns a number, called a GUID, to each entity in order to uniquely identify it for the discovery process to work correctly. You can control how to set the GUID using the value assigned to rtps_auto_id_kind . For more information, see Controlling How the GUID is Set ( ...
5106 reads — 0 comments
RTI Connext DDS uses a special discovery mechanism that allows RTI Tools such as Admin Console to find participants on different domains. The messages that make this possible are called default domain announcements. RTI Connext provides a couple of QoS settings that allow this special discovery ...
5810 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities