RTI Core Libraries and Utilities

Enabling monitoring library in an application may result in a valgrind memory leak report.

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 ...
bobby
Tue, 08/28/2018 - 16:03
3605 reads — 0 comments

What happens if I rename the RTI Connext DDS installation directory?

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 ...
sonia
Wed, 07/25/2018 - 03:16
2656 reads — 0 comments

QoS configurations for transport when starting applications with network interfaces disabled for IP mobility use case.

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. ...
pranjali
Tue, 03/20/2018 - 12:46
6943 reads — 0 comments

Why two applications cannot communicate using shared memory when their network interface cards are different

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 ( ...
acasado
Wed, 12/20/2017 - 07:43
4122 reads — 0 comments

Using default domain announcements to find participants on different domains

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 ...
Marc.Chiesa
Tue, 12/19/2017 - 14:33
4238 reads — 0 comments

Deploying an RTI Connext DDS Application with Docker

This article assumes familiarity with Docker. For instance, you should know the difference between containers and images, and the purpose of a Dockerfile. If not, visit www.docker.com and get up to speed on Docker basics before reading further. Introduction In this example, we’ll build and deploy a ...
Mike Partington
Tue, 11/28/2017 - 12:12
9812 reads — 0 comments

Creating a Docker image with RTI Connext DDS

This article assumes familiarity with Docker. For instance, you should know the difference between containers and images, and the purpose of a Dockerfile. If not, then visit www.docker.com and get up to speed on Docker basics before reading further. Introduction In this example, we’ll create a ...
Mike Partington
Wed, 11/22/2017 - 11:47
10786 reads — 4 comments

How to use RTI Connext DDS to Communicate Across Docker Containers Using the Host Driver

When using the “host” Docker driver, all network interfaces of the host machine are accessible from the Docker container. Furthermore, there is no networking namespace separation between the Docker containers and the host machine. To run a container in host mode, run the following command: $ docker ...
israel
Mon, 10/30/2017 - 10:16
11881 reads — 0 comments

Multicast for data transfer, for applications on the same node

Multicast over UDPv4 can be used for data transfer between applications that are running on the same machine, even if shared memory is enabled. RTI's Connext DDS provides various transports, which can be configured using the USER_QOS_PROFILES.xml file. The most commonly used transports are shared ...
chirags
Mon, 10/16/2017 - 16:08
4287 reads — 0 comments

Communicate between two Docker containers using RTI Connext DDS and shared memory

Introduction Docker enables containers to communicate with one another and with the host machine using interprocess communication (IPC). As explained in the Docker’s documentation: IPC (POSIX/SysV IPC) namespace provides separation of named shared memory segments, semaphores and message queues. ...
israel
Mon, 10/02/2017 - 09:52
13014 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities