LynxOS

Note: Applies to Connext DDS 5.x and above Sending TypeCode/TypeObject on the wire provides convenience over specifying the type via XML configuration, but has the disadvantage that more data must be sent during endpoint discovery. This can cause network congestion problems when the TypeCode/ ...
1480 reads — 0 comments
Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
10046 reads — 7 comments
Note: Applies to RTI Connext 4.x and above. The following error: [D0004|CREATE Participant|D0004|ENABLE] NDDS_Transport_Shmem_is_segment_compatible:incompatible shared memory protocol detected. Current version 1.0 not compatible with 2.0. is caused when two applications, one using RTI Connext DDS 4 ...
4004 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 ...
2725 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 ...
3797 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. ...
1533 reads — 0 comments
Subscribe to RSS - LynxOS