Solutions

Note: Applies to RTI Connext 4.x and above The narrow method is a class-scope method that implements a safe down-cast for a pointer to an RTI Connext entity. It is a type-safe way to cast a pointer. The Java API does not require this method because Java casts are always type-safe. This method takes ...
6279 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.2 and 4.3 RTI Data Distribution Service 4.2 and 4.3 applications and tools are interoperable, with the following caveats. To monitor a 4.2 application with 4.3 tools: If your 4.2 application's data types do not contain any 8-byte or larger primitive ...
2675 reads — 0 comments
Note: Applies to RTI DDS 4.0x. The following applies to RTI DDS 4.0g (or earlier). This problem has been corrected in RTI DDS 4.0h and later. You may see a deadlock problem during application shutdown, with or without an error message. This deadlock is typically seen when the value for the ...
5694 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 ...
7738 reads — 0 comments
Note: Applies to NDDS 3.x. NDDS's internal time representation is in NTP format rather than DDS_Time for computational efficiency reasons. The header osapi/osapi_ntptime.h defines NTP time class ( struct RTINtpTime ) as well as its manipulation methods. A brief excerpt from this header file is ...
3473 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.2 and later The error observed may be similar to the following: The library nddsjavad.dll could not be loaded on Windows. Make sure that the library is in your Path environment variable. Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\ ...
5530 reads — 1 comment
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 ...
14469 reads — 0 comments

Pages