Solutions

Note: Applies to RTI Data Distribution Service 4.1 and 4.2 If a non-keyed DataReader calls take() or read() while max_samples (in the ResourceLimitsQosPolicy ) is LENGTH_UNLIMITED (the default), and, the available data is greater than max_samples_per_read (in the DataReaderResourceLimitsQosPolicy ...
3073 reads — 0 comments
Note: Applies to RTI Connext 4.2 and above To prevent deadlocks, RTI uses mutexes to coordinate access to critical data and operations between threads. Mutexes are grouped in Exclusive Areas (EAs) code based on the regions they protect. However, deadlocks are still possible if you try to use ...
5303 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The first and foremost step to reducing the memory footprint is an architectural review. The number of topics, the queue sizes, whether or not you use keys, the number of domains, or the usage of partitions have a great impact on the memory footprint of ...
6524 reads — 0 comments
The short answer is that you need to remove the trailing backslash from your NDDSHOME environment variable. The rtiddsgen code generator calls a Java program within a batch script. This script passes %NDDSHOME% as a define argument to java. If NDDSHOME ends with a backslash, the shell escapes the ...
5768 reads — 0 comments
RTI Connext operates across the host layers (4,5,6,7) using an existing Network, Data Link and Physical layer. RTI Connext's Layer 4 interaction is a little bit open to interpretation; RTI Connext uses an existing layer 4 transport (UDP). The RTPS protocol adds reliability and other QoS to it to ...
6387 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. RTI Connext calls fopen() to load the default XML and NDDS_DISCOVERY_PEERS files if they exist. On some VxWorks targets that either have no file system or use NFS, FTP, or some other network-based file system, and the file system is not mounted, RTI ...
4714 reads — 0 comments
The following error may appear when you upgrade or install a new version of RTI Analyzer over the same workspace that was used by a previous version of RTI Analyzer. CapturingAgentManager initialized, but did not find any valid capturing agent installed Creating a new workspace should fix the ...
3511 reads — 0 comments

Pages