RTI Core Libraries and Utilities

How do I minimize the memory footprint and avoid dynamic memory allocation?

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 ...
gianpiero
Thu, 01/17/2013 - 12:19
8502 reads — 0 comments

Why do I see a Java 'usage' error when I run rtiddsgen on Windows?

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 ...
gianpiero
Thu, 01/17/2013 - 12:15
7147 reads — 0 comments

At what OSI layers does RTI Connext operate?

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 ...
alex
Thu, 01/17/2013 - 12:12
8349 reads — 0 comments

How do I eliminate the long startup delay on some VxWorks targets with no file system?

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 ...
ken
Thu, 01/17/2013 - 12:10
6426 reads — 0 comments

Why does rtiddsgen require a C preprocessor for its code generation? Why does rtiddsgen try to locate cc1plus?

Before processing an IDL file, rtiddsgen attempts to run a C preprocessor to support #if tests and related preprocessor directives. There are several options you can pass to rtiddsgen to control preprocessor use, including: -ppDisable (formerly -ppNotRun ) : Don't use the C preprocessor -ppPath : ...
alex
Thu, 01/17/2013 - 12:07
5688 reads — 0 comments

Why is multicast not working on my LynxOS target?

Note: Applies to NDDS 3.x, RTI Connext 4.x and above. The LynxOS 4.0 IP stack (and many other BSD-derived network stacks) will fail to send multicast messages unless there is an entry in the routing table that matches the destination multicast IP address. In practice, this means that either: a ...
memo.salas
Thu, 01/17/2013 - 12:07
5723 reads — 0 comments

What does "shmat() failure, error 0x18" mean on a Solaris system?

This solution addresses the following error message on Solaris systems: RTIOsapiSharedMemorySegment_attach:OS shmat() failure, error 0X18 NDDS_Transport_Shmem_attach_writer:failed to initialize shared memory resourcesegment for key 0x4020d0 Error message 0x18 on a Solaris system means that the ...
gianpiero
Thu, 01/17/2013 - 12:07
5936 reads — 0 comments

Why can't I communicate over loopback, but can using shared memory?

NOTE: Applies to RTI Data Distribution Service 4.1 and 4.2 By default, RTI Data Distribution Service uses shared memory to communicate with other DomainParticipants on the same node and disables local traffic over the UDPv4 or UDPv6 loopback interface. So, by default, an RTI Data Distribution ...
abhi
Thu, 01/17/2013 - 12:07
7686 reads — 0 comments

How do I change the multicast time-to-live (TTL)?

Note: Applies to RTI Connext 4.x and above RTI Connext 4.x and above uses a default multicast time-to-live (TTL) value of 1. This means that, by default, multicast traffic will not cross subnet boundaries. The TTL value can be adjusted in the transport property. Method One for modifying the TTL ( ...
waffletchnlgy
Thu, 01/17/2013 - 12:06
17387 reads — 0 comments

Why doesn't my RTI Connext application communicate with an RTI Connext application installed as a Windows Service?

Note: Applies to RTI Connext 4.x and above. An RTI Connext application installed as a Windows Service application (formerly known as an NT service) will not communicate over shared memory with a DDS application that is not installed as a Windows Service. This is due to the namespace used to create ...
vishal
Thu, 01/17/2013 - 12:05
7669 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities