Solutions

Example Code - Achieving 'Batching' by setting push-on-write to false

Note: Applies to RTI Connext 4.0 and above. This example shows how to achieve batching without using the Batch QoS policy (which was introduced in 4.4). Publisher This Publisher sends out bursts of 32 keyed reliable samples at 20Hz. The point here is that the dataWriterQos.protocol.push_on_write = ...
ken
Thu, 01/17/2013 - 12:32
5988 reads — 0 comments

Why do I see "Error storing RTI DDS sample in table 'database.tablename'" in the RTC console when subscribing to data?

Note: Applies to RTI Real-Time Connect 4.x and above. One possible reason might be your ODBC driver. The following error may appear when RTI Real-Time Connect tries to store a sample and after creating a new entry in the RTC database table RTIDDS_SUBSCRIPTIONS , such as table_history_depth : RTI ...
erin
Thu, 01/17/2013 - 12:31
3842 reads — 0 comments

How can I improve performance on Windows under a heavy load?

When running a subscribing application on a Windows system under heavy load (such as when running performance tests), you may experience erratic behavior when receiving samples, due to reassembly failures. You may see that the application temporarily stops receiving data. You can verify this ...
alex
Thu, 01/17/2013 - 12:31
19936 reads — 2 comments

Why don't I see any builtin topic data when subscribing to DDS_TopicBuiltinTopicData?

Note: Applies to RTI Data Distribution Service 4.1 and above. The DDS_TopicBuiltinTopicData built-in topic is meant to convey information about discovered Topics. It is a known issue in RTI Data Distribution Service 4.1 and 4.2 that these topic samples are not propagated in a separate packet on the ...
edward
Thu, 01/17/2013 - 12:28
2600 reads — 0 comments

What does the "can't reach: locator" error message mean?

Note: Applies to RTI Connext 4.x. In general, a can't reach:locator: error message means that a DataWriter cannot send to the locator of a DataReader , usually due to a transport configuration error. For example, suppose Participant A has both the UDPv4 and shared-memory built-in transports enabled ...
vishal
Thu, 01/17/2013 - 12:24
26994 reads — 2 comments

Why does my subscriber report multiple liveliness change events when I kill my publisher?

Note: Applies to RTI Connext 4.x and above. Upon changing the liveliness lease duration of both the DataReader and DataWriter , and instrumenting the on_liveliness_changed() listener callback on the reader side, you will see the callback is called twice when you kill the publishing application. ...
gianpiero
Thu, 01/17/2013 - 12:23
5855 reads — 0 comments

What does it mean when RTI Monitor shows only DomainParticipants and a "Topics" category with no actual Topics listed under it?

When RTI Monitor is not getting updates from RTI Monitoring Library, the left-hand Physical View looks similar to the following, showing one or more DomainParticipants and a Topics category, but no DataReaders, DataWriters, or Topics listed under the Topics category: This indicates that RTI Monitor ...
ken
Thu, 01/17/2013 - 12:23
8650 reads — 1 comment

Pages