Solutions

Howto limit the size of the log files

Note: RTI Connext 5.3.0 and above has new options in the LoggingQosPolicy, which allow limiting the size of RTI Connext Log Files in an easy way. Prior to RTI Connext 5.3.0, a custom device had to be set for this purpose. This article has been updated to cover both methods of limiting the size of ...
Juanjo Martin
Tue, 03/19/2013 - 01:34
8564 reads — 0 comments

What error: Reliable large data requires asynchronous write

Note: Applies to RTI Connext 7.3.0 and below. Starting in release 7.4.0, asynchronous publishing is no longer a requirement for reliable, large data. The error " COMMENDSrWriterService_on_Submessage:!write resend. Reliable large data requires asynchronous write " is due to having a data type that ...
dstockdill
Thu, 03/07/2013 - 06:09
11622 reads — 0 comments

What causes this error: "NDDS_Transport_Shmem_attach_writer:incompatible shared memory segment found."

Note: Applies to RTI Connext 4.x and above. When you have multiple applications running on a single machine utilizing the shared memory transport this error will occur of when the shared memory transport property dds.transport.shmem.builtin.parent.message_size_max is not consistent across all RTI ...
irwin
Thu, 02/21/2013 - 12:36
11524 reads — 1 comment

What causes this error: "NDDS_Transport_UDPv4_SocketFactory_create_receive_socket: No interface found enabled for multicast"

Note : Applies to RTI Connext DDS 4.4 and above The following error: NDDS_Transport_UDPv4_SocketFactory_create_receive_socket: No interface found enabled for multicast. happens when a DomainParticipant is created with UDPv4 transport enabled (which is the default value) and all network interfaces ...
Juanjo Martin
Tue, 02/19/2013 - 03:58
10461 reads — 0 comments

What causes this error: "NDDS_Transport_UDPv4_receive_rEA:!precondition: buffer_in->length < (self)->property->message_size_max"

The following error: NDDS_Transport_UDPv4_receive_rEA:!precondition: buffer_in->length < (self)->property->message_size_max is caused when the buffer size of the Receiver Pool is less than the message_size_max of a builtin transport (UDPv4 in this case). To fix this issue, all you need ...
Juanjo Martin
Tue, 02/12/2013 - 01:58
7088 reads — 0 comments

What causes this error: "incompatible shared memory protocol detected."

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 ...
bobby
Wed, 02/06/2013 - 14:05
5807 reads — 0 comments

How do I separate the transport used for discovery data from the transport used for user data?

Note: Applies to RTI Connext version 4.x and above OMG Data Distribution Service (DDS) applications send two types of data: meta data used for discovery and user data. Because the core of RTI Connext DDS is transport agnostic, it does not make any assumptions about the actual transports used to ...
erin
Fri, 02/01/2013 - 17:18
5980 reads — 0 comments

Pages