Solutions

Note: Applies to RTI Connext 4.x and above. RTI Connext uses the concept of exclusive areas (EA) to avoid deadlocks when user listener code calls the RTI Connext APIs. In a nutshell: Each entity has their own EAs. Controlling access into EAs is a way to prevent deadlocking situations. The rule of ...
5484 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. Specific to LynxOS . The error message " icmp-response bandwidth limit " in LynxOS is caused by too many messages sent to ports that are not being listened on by an application. LynxOS sends an icmp-response packet for each incoming message and when those ...
5059 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above Yes, RTI Connext will cause IGMP messages to be sent, allowing routers to appropriately handle multicast traffic delivery. The RTI code does not send the IGMP messages itself, but the host's network stack should send them when needed. When RTI ...
5324 reads — 0 comments
Note: Applies to RTI Connext 4.x and above, C and C++ APIs Statically allocated arrays For C, use FooSeq_to_array . For C++, use FooSeq::to_array . Dinamically allocated arrays There is an easy way to copy from sequence into an array. RTI Connext will always create a contiguous internal buffer for ...
7210 reads — 1 comment
Note: Applies to RTI Connext 4.x and above These are some common errors when specifying the key in the IDL: In the IDL file, you must use //@key after the key field. Do not use a space between any of these characters: //@key Also note that the directive is case-sensitive — use all lower case. Only ...
3088 reads — 0 comments
Note: Applies to RTI Connext 4.x and above If you have an RTI Connext application running on a QNX machine and it is unable to communicate with other applications running on the same machine started by another user, or if your application fails to start (with an error related to shared memory), ...
6070 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The LynxOS version does not have a multicast address in its peer host list by default. You need to modify the initial_peers list in the Discovery QoS policy to either include the multicast address, or to explicitly list the hosts that need to communicate. ...
2185 reads — 0 comments

Pages