RTI Core Libraries and Utilities

This message can be recieved when creating a new reader listening on a multicast group: setsockopt(ADD_MEMBERSHIP) error 0X62 The hex code may differ across platforms — EADDRINUSE is 98 on Linux, 125 on Solaris — check your system's errno.h to be sure. RTI middleware can share receive-resources ...
7223 reads — 1 comment
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 ...
9250 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. Upon changing the liveliness lease duration of both the DataReader and DataWriter , and instrumenting the on_liveliness_changed() listener callback on the reader side, you will see the callback is called twice when you kill the publishing application. ...
6130 reads — 0 comments
The short answer is that only the platforms listed in the Release Notes are supported. A platform is defined by a CPU architecture, an operating system and its version, and a compiler version. For example, i86Linux2.6gcc4.1.1 means Linux 2.6 on an Intel processor with version 4.1.1of the gcc ...
3778 reads — 0 comments
Yes, you can run your RTI Connext-based application on a virtual machine. Make sure that any time synchronization or jumps occur before starting your RTI Connext application. In versions 4.4b and higher, we have improved support for virtual machines by introducing a feature to specify which clock ...
3275 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1 and 4.2 If a non-keyed DataReader calls take() or read() while max_samples (in the ResourceLimitsQosPolicy ) is LENGTH_UNLIMITED (the default), and, the available data is greater than max_samples_per_read (in the DataReaderResourceLimitsQosPolicy ...
3657 reads — 0 comments
Note: Applies to RTI Connext 4.2 and above To prevent deadlocks, RTI uses mutexes to coordinate access to critical data and operations between threads. Mutexes are grouped in Exclusive Areas (EAs) code based on the regions they protect. However, deadlocks are still possible if you try to use ...
6117 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The first and foremost step to reducing the memory footprint is an architectural review. The number of topics, the queue sizes, whether or not you use keys, the number of domains, or the usage of partitions have a great impact on the memory footprint of ...
7588 reads — 0 comments
The short answer is that you need to remove the trailing backslash from your NDDSHOME environment variable. The rtiddsgen code generator calls a Java program within a batch script. This script passes %NDDSHOME% as a define argument to java. If NDDSHOME ends with a backslash, the shell escapes the ...
6571 reads — 0 comments
RTI Connext operates across the host layers (4,5,6,7) using an existing Network, Data Link and Physical layer. RTI Connext's Layer 4 interaction is a little bit open to interpretation; RTI Connext uses an existing layer 4 transport (UDP). The RTPS protocol adds reliability and other QoS to it to ...
7520 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities