RTI Core Libraries and Utilities

Note: Applies to Connext DDS 5.x and above Sending TypeCode/TypeObject on the wire provides convenience over specifying the type via XML configuration, but has the disadvantage that more data must be sent during endpoint discovery. This can cause network congestion problems when the TypeCode/ ...
365 reads — 0 comments
The following three configurations are related to detecting issues on the TCP connections. Although they seem similar, they enable different features with subtle differences. Connection Liveliness When the Connection Liveliness feature is enabled, RTI TCP Transport Liveliness Request and Response ...
236 reads — 0 comments
When we call DataWriter::write() , we expect to see a user data packet sent on the wire, but under what conditions will Connext DDS send packets of its own accord? There are many reasons why Connext DDS may send messages other than user data. Some of the more common reasons are described below. ...
456 reads — 0 comments
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. ...
555 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 ...
773 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 ...
665 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 ...
747 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 ...
726 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 ...
983 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 ...
940 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities