Solutions

This solution is only a workaround until the Request/Reply API is available in LabVIEW. This will only work for one Requester and one Replier. The Request/Reply communication pattern is pretty useful for industrial applications. It is quite normal to have an application requesting an action to ...
19739 reads — 10 comments
If you create a large number of instances or entities and there is insufficient thread stack space, you can get the following error: REDAFastBufferPool_getBuffer:!precondition: pool==((void *)0) REDASkiplistNode_new:!create node REDASkiplist_assertNodeEA:!create node ...
4396 reads — 0 comments
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 ...
5596 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 ...
10387 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 ...
4436 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 ...
4235 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, ...
4494 reads — 0 comments

Pages