Solutions

Applies to RTI Connext 4.x and above With default settings, the maximum number of domains and participants in the same machine is limited as follows: Versions 4.1e and lower: 100 domains (0 .. 99) and 58 participants (0 .. 57) per domain when the domain ID is 0. Version 4.2e and higher: 233 domains ...
18379 reads — 3 comments
Note: Applies to RTI Developer Platform 1.1.3 and 1.2.1. FlexLM is no longer a dependency for RTI Connext 4.5x and above. When starting RTI Developer Platform on a Linux system, you will see the following error if your system lacks the correct libstdc++.so library: RTI Developer Platform failed to ...
2511 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The TryEnterCriticalSection function is only declared in WinBase.h if _WINNT_WIN32 >= 0x400 . This symbol is defined within the ACE-TAO headers, which in turn are pulled in from Foo.h . If an application includes ndds/ndds_cpp.h before including Foo.h ...
2510 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.2x, 4.3x, and 4.4x. Designed to work with RTI Connext, RTI Developer Platform is a set of tools that provide powerful insight and comprehensive analysis of your distributed data network. They will simplify your distributed system development and make ...
3617 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. If the publisher and subscriber applications use different data-type definitions (IDL) for the same topic, it is common to see the following messages reported by the RTI middleware: Prior to 4.4c Unkeyed Data PRESPsReaderQueue_storeQueueEntry:!deserialize ...
6842 reads — 2 comments
Note: Applies to RTI NDDS 3.x. Error message: NDDS Alarm: Unable to serialize fired message NDDS Alarm: Alarm event: 129 period: 0.249996781 next time: 190.643200517 task 1512 This message most likely indicates that NDDS was unable to use the stack to send a local UDP message. It is usually caused ...
1957 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1f. MIGGeneratorSample_setParameterLength() error messages are caused by a bug when RTPS GAP messages are NACKed by a reliable reader. This error can result in memory corruption. DataWriters issue RTPS GAP messages to indicate that samples are no ...
1701 reads — 0 comments

Pages