Solutions

A normal scenario in RTI Connext DDS is to have a Publisher that generates samples and several Subscribers that receive the generated data. In other words, the expected out-of-the-box behavior is for all Subscribers to get all the data. This is so because each Subscriber has its own DataReader for ...
6209 reads — 0 comments
There are some situations in which two applications, even though they have been configured to have each other in their initial peers lists, will not discover each other. Two applications are on the same machine and have only either 127.0.0.1 or "localhost" in their initial peers lists AND ...
11821 reads — 0 comments
When running on Microsoft Windows, the Routing Service 5.1.0 can unexpectedly stop working with the following dialog being displayed: This can also occur when terminating the application with Ctrl-C. The problem might be caused by a bug in an optimization introduced in Routing Service 5.1.0 that ...
4935 reads — 0 comments
Note: This solution applies to RTI Connext DDS 5.1.0. The Heartbleed bug, which causes a serious security threat, has been recently identified in certain versions of the OpenSSL cryptographic software library. More information about the bug can be found at www.heartbleed.com . OpenSSL is used for ...
4732 reads — 0 comments
When viewing recorded data in a database created by RTI Recording Service, if you see gaps in the column of publishing sequence number, it might not indicate that there were samples lost during recording. This can happen when a DataWriter explicitly calls unregister_instance() with the QoS policy, ...
5004 reads — 0 comments
When running two applications on the same WindRiver VxWorks target, one in kernel mode and the other in RTP mode, the two applications will not discover each other when using out of box settings in RTI Connext. The reason this occurs has to do with how RTI Connext internally marks the individual ...
7467 reads — 0 comments
If the logic of your application requires to spawn new threads, and in those threads you are calling a DDS API such as write() , you may notice a memory growth. To ensure that all the resources allocated in that thread are correctly released, remember to call unregister_thread() right before ...
5393 reads — 0 comments

Pages