RTI Core Libraries and Utilities

What causes this error: "PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2"

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 ...
belen
Wed, 03/25/2015 - 10:05
7998 reads — 7 comments

WaitSets: What can I do to reduce my CPU usage?

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 ...
sonia
Wed, 01/28/2015 - 16:47
2612 reads — 0 comments

Why do I see a packet that starts by RTPX instead of RTPS?

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 ...
Juanjo Martin
Tue, 01/20/2015 - 08:09
1919 reads — 0 comments

What causes this error: "COMMENDBeReaderService_onSubmessage:!get ber remoteWriter"

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. ...
belen
Thu, 01/08/2015 - 03:47
1406 reads — 0 comments

How can I reduce the discovery time?

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 ...
Juanjo Martin
Thu, 08/07/2014 - 03:00
4493 reads — 0 comments

What error can occur if a thread stack_size is not large enough?

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 ...
bobby
Thu, 07/24/2014 - 23:27
2188 reads — 0 comments

I Put My Machines In My Initial Peers Lists -- Why Don’t They Discover Each Other?

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 ...
erin
Mon, 07/07/2014 - 14:26
4594 reads — 0 comments

RTI Connext DDS and the OpenSSL Heartbleed Bug

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 ...
bobby
Mon, 04/28/2014 - 16:47
2030 reads — 0 comments

On VxWorks, an RTP application can not discover a kernel application over shared memory

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 ...
bobby
Fri, 04/04/2014 - 14:05
3077 reads — 0 comments

Failure to Create a Participant due to Insufficient Shared Memory Kernel Settings

If you are running RTI Connext DDS 5.1.0 or earlier, you may get this error message when starting your application: [D0061|ENABLE]NDDS_Transport_Shmem_create_recvresource_rrEA:failed to initialize shared memory resource segment for key 0x405971 [D0061|ENABLE] ...
jmorales
Tue, 04/01/2014 - 13:53
8156 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities