RTI Core Libraries and Utilities

Example Code - Achieving 'Batching' by setting push-on-write to false

Note: Applies to RTI Connext 4.0 and above. This example shows how to achieve batching without using the Batch QoS policy (which was introduced in 4.4). Publisher This Publisher sends out bursts of 32 keyed reliable samples at 20Hz. The point here is that the dataWriterQos.protocol.push_on_write = ...
ken
Thu, 01/17/2013 - 12:32
6975 reads — 0 comments

Why don't I see any builtin topic data when subscribing to DDS_TopicBuiltinTopicData?

Note: Applies to RTI Data Distribution Service 4.1 and above. The DDS_TopicBuiltinTopicData built-in topic is meant to convey information about discovered Topics. It is a known issue in RTI Data Distribution Service 4.1 and 4.2 that these topic samples are not propagated in a separate packet on the ...
edward
Thu, 01/17/2013 - 12:28
3069 reads — 0 comments

What do 'setsockopt ADD_MEMBERSHIP' errors mean?

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 ...
gianpiero
Thu, 01/17/2013 - 12:28
8244 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
10705 reads — 0 comments

Why does my subscriber report multiple liveliness change events when I kill my publisher?

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. ...
gianpiero
Thu, 01/17/2013 - 12:23
6631 reads — 0 comments

Can I use a (gcc) compiler version different from what is listed in the Release Notes?

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 ...
dstockdill
Thu, 01/17/2013 - 12:23
4408 reads — 0 comments

Can I run my RTI Connext application in a virtual machine?

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 ...
abhi
Thu, 01/17/2013 - 12:22
3674 reads — 0 comments

What might cause a segmentation fault while reading data? Why do I see an unexpected data sequence length?

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 ...
alex
Thu, 01/17/2013 - 12:21
4086 reads — 0 comments

How can I prevent deadlocks while invoking the RTI APIs from a Listener?

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 ...
elaine
Thu, 01/17/2013 - 12:19
6752 reads — 0 comments

How do I minimize the memory footprint and avoid dynamic memory allocation?

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 ...
gianpiero
Thu, 01/17/2013 - 12:19
8360 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities