shared memory

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
14542 reads — 0 comments

How to capture traffic if my Connext DDS applications are communicating through shared memory

Wireshark and tcpdump are very powerful tools which you can use to capture traffic. They may come in handy when debugging issues with your DDS applications. These tools can capture all kinds of packets: RTPS, UDP, TCP, IP… However, they cannot capture traffic if your applications are communicating ...
Francisco Porcel
Fri, 07/28/2017 - 07:38
46606 reads — 0 comments

What causes this error: "incompatible shared memory protocol detected."

Note: Applies to RTI Connext 4.x and above. The following error: [D0004|CREATE Participant|D0004|ENABLE] NDDS_Transport_Shmem_is_segment_compatible:incompatible shared memory protocol detected. Current version 1.0 not compatible with 2.0. is caused when two applications, one using RTI Connext DDS 4 ...
bobby
Wed, 02/06/2013 - 14:05
5809 reads — 0 comments

What are possible solutions to common shared memory issues?

Note: Applies to RTI Data Distribution Service 4.x and above. First, we need some background to understand how RTI's shared-memory transport works. The RTI Data Distribution Service shared-memory transport uses different standards to access shared mutexes and shared-memory segments, depending on ...
waffletchnlgy
Thu, 01/17/2013 - 12:46
60851 reads — 1 comment

How much shared memory is required by RTI Connext applications?

Note: Applies to RTI Connext 4.x and above. By default, every time you create a DDS participant with SHMEM transport enabled, the middleware creates two shared memory segments: one to receive discovery traffic and one to receive user traffic. Each one of the shared memory segments will contain a ...
gianpiero
Thu, 01/17/2013 - 12:26
7722 reads — 0 comments

What does "shmat() failure, error 0x18" mean on a Solaris system?

This solution addresses the following error message on Solaris systems: RTIOsapiSharedMemorySegment_attach:OS shmat() failure, error 0X18 NDDS_Transport_Shmem_attach_writer:failed to initialize shared memory resourcesegment for key 0x4020d0 Error message 0x18 on a Solaris system means that the ...
gianpiero
Thu, 01/17/2013 - 12:07
4679 reads — 0 comments

Why can't I communicate over loopback, but can using shared memory?

NOTE: Applies to RTI Data Distribution Service 4.1 and 4.2 By default, RTI Data Distribution Service uses shared memory to communicate with other DomainParticipants on the same node and disables local traffic over the UDPv4 or UDPv6 loopback interface. So, by default, an RTI Data Distribution ...
abhi
Thu, 01/17/2013 - 12:07
6224 reads — 0 comments
Subscribe to RSS - shared memory