Solutions

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 ...
5200 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 ...
3875 reads — 0 comments
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 : ...
4519 reads — 0 comments
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 ...
4792 reads — 0 comments
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 ...
4888 reads — 0 comments
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 ...
6470 reads — 0 comments
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 ( ...
14775 reads — 0 comments

Pages