RTI Core Libraries and Utilities

You can speed up participant deletion by decreasing the value of QoS property shutdown_cleanup_period . Before a participant can be deleted it must clean up its internal database. This property specifies the wake up period for the thread that takes care of this. The default value is set to 1 second ...
1314 reads — 0 comments
In complex systems, it may happen that one node gets overloaded and it stops communicating (or communicate slower) with remote nodes. If this node contains a DataReader that is subscribed to a topic along with other remote DataReaders, it can make the other DataReaders stop receiving data when the ...
898 reads — 0 comments
If you are inheriting from either the BuiltinQosLibExp::Generic.HighThroughput or the BuiltinQosLibExp::Generic.AutoTuning built-in QoS profiles, your DataWriters and DataReaders may fail to communicate if you are writing small samples. In version 5.1.0, if you were writing samples smaller than 384 ...
1215 reads — 0 comments
If you are running into problems compiling the shipped examples or the generated Hello World example from rtiddsgen on a non-Windows platform, one of the first things to check is if your installation directory resides in a path that contains spaces. If it does, then the solution will be to redefine ...
4304 reads — 0 comments
Description The discovery phase in DDS applications can be considered a high throughput scenario under some circumstances. Some examples are: The applications have a lot of DDS entities. More than 2 hosts are involved. The type definitions are sent within the discovery packets (i.e., TypeCode and ...
4131 reads — 0 comments
The following examples demonstrate how to use the Modern C++ API: New! Flat Data and Zero Copy Latency (C++11) New! Flat Data API (C++11) Lambda Content Filter (C++11) Content Filtered Topic (C++03) Asynchronous Publisher (C++03) Batching and Turbo Mode (C++03) Builtin Topics (C++03) Listeners (C++ ...
6460 reads — 0 comments
In a scenario where multiple DataWriters come up and go away in the system, a matching DataReader application will experience a continual memory growth, this may be confused with a memory leak. This observed behavior is due to the fact that DataReader entities must maintain information about the ...
2477 reads — 0 comments
RTI Connext DDS uses multicast for the discovery process in the default setting. When a host needs to join a multicast group, the network stack of the host sends out an IGMP Membership Report message also known as the join message. These messages are forwarded through the LAN to the local IGMP ...
3137 reads — 0 comments
Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
7235 reads — 6 comments
For high-rate data, the usage of a WaitSet may lead to a very high CPU usage if the WaitSet wakes up too often. By default, a WaitSet is created without any properties specified. In this case, the WaitSet wakes up immediately every time a trigger event occurs. However, "waking up" involves a ...
2479 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities