Troubleshooting

Note : Applies to RTI Connext 4.x and above. The message MIGGenerator_addData:serialize buffer too small indicates that the transport-buffer size is too small for the data being sent and needs to be increased. When the transport layer is initialized, it allocates enough resources to serialize/ ...
2009 reads — 0 comments
Note: Applies to NDDS 3.x and earlier, RTI Data Distribution Service 4.0 and 4.1 To monitor the state of the data buffer usage inside the stack, you can use the netStackDataPoolShow or mbufShow functions. Both commands give the same information. If the stack has been running out of clusters, these ...
4300 reads — 0 comments
Note: Applies to RTI Connext 4.x This solution addresses the following exception: PRESParticipant_assertRemoteParticipant:!assert remote participant c0c80aa3 7e520001 due to different ro area DISCDynamicParticipantSelfDetector_onDataAvailable:!assert remote participant The likely cause of this ...
11456 reads — 0 comments
Note: Applies to RTI Connext 4.x and above Problem You are trying to create a new DomainParticipant and see error messages about an invalid port and/or a failure to create a receive resource . For instance: [D0001|ENABLE]NDDS_Transport_UDPv4_Socket_bindWithIp:0X1CF2 in use [D0001|ENABLE] ...
2771 reads — 0 comments
Note : Relevant RTI Connext version 4.x and above. In order to guarantee that RTI Connext will deliver all messages, both the data writer and data reader must be configured for strict reliable communication. Strict reliability ensures that every message will be received by all known data readers. ...
6681 reads — 0 comments
Note : Applies to RTI NDDS 2.x and earlier, and NDDS 3.x. This Solution describes errors you may see when running an NDDS application on VxWorks 5.4.x or 5.5.x. These error messages most likely mean that the amount and/or sizing of your stack buffers are incorrect. NDDS is unable to send "NDDS ...
2529 reads — 0 comments
Prior to RTI Data Distribution Service version 4.4, receiving data over multicast could only be configured on the reader side. The reader Qos specifies to the writer that it wants to receive data using a multicast address. Starting with RTI Data Distribution Service 4.4, in addition to the ...
6037 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. Discovery is not an instantaneous event. It takes some time for the discovery process between applications to complete. The DDS DataWriter and DDS DataReader must discover each other before they can start communicating. Therefore, if you send data ...
8920 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.0 and 4.1 If you notice unexpected behavior (for example, unintended functions getting called, object creation failing, etc.), check your current stack margin by running the command checkStack . If the margin is low, this is a possible explanation of ...
6778 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. RTI Connext uses the concept of exclusive areas (EA) to avoid deadlocks when user listener code calls the RTI Connext APIs. In a nutshell: Each entity has their own EAs. Controlling access into EAs is a way to prevent deadlocking situations. The rule of ...
3282 reads — 0 comments

Pages

Subscribe to RSS - Troubleshooting