RTI Core Libraries and Utilities

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 ...

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 ...

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++03) Polling QueryCondition (C++03) Ordered Presentation (C++11) Recursive Data Type (C++03) DynamicData nested types (C++03) DynamicData publish and subscribe (C++11) DynamicData acess to union discriminator (C++03 and C++11) Partitions (C++03) Builtin Qos Profiles (C++03) Get Publishers (C++03) Using QoS Profiles (C++03) WaitSets (C++03) WaitSet with Query Conditions (C++11) WaitSet with Status Conditions (C++03) Custom Content Filters (C++03) DynamicData Accessing Sequence Members (C++03) Keyed Data (C++03) Coherent Presentation (C++03) Content Filtered Topic -- String Filter (C++03) Keyed Data Advanced (C++03) Ordered Presentation Group (C++03) Time-based Filters (C++03) Custom Flow Controllers (C++03) Deadline and Content Filtering (C++03) Multichannel (C++03) Using Type Codes (C++03) Polling Read (C++03) ...

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 ...

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 ...

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 ...

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 ...

Packets starting by RTPX are default domain discovery announcements. This is a new non-standard packet introduced in Connext 5.1.0 to help the tools discover applications running in other domains (for instance, RTI Admin Console). This packet is sent to the default multicast address and port for ...

The following error during shutdown: COMMENDBeReaderService_onSubmessage:!get ber remoteWriter indicates that a DataReader has received a sample but the corresponding remote DataWriter has already been deleted. If you are shutting down your entire system, you can probably ignore this message. ...

For complex systems with hundreds of participants and endpoints, discovery may cause long startup times and high network utilization. There are several options that help increase discovery performance: 1) Reduce the size of discovery packets 1.1. You can configure the middleware to not send the ...