Solutions

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 ...
23463 reads — 1 comment
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. ...
5329 reads — 0 comments
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 ...
7558 reads — 1 comment
The short answer is that only the platforms listed in the Release Notes are supported. A platform is defined by a CPU architecture, an operating system and its version, and a compiler version. For example, i86Linux2.6gcc4.1.1 means Linux 2.6 on an Intel processor with version 4.1.1of the gcc ...
2943 reads — 0 comments
Yes, you can run your RTI Connext-based application on a virtual machine. Make sure that any time synchronization or jumps occur before starting your RTI Connext application. In versions 4.4b and higher, we have improved support for virtual machines by introducing a feature to specify which clock ...
2691 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1 and 4.2 If a non-keyed DataReader calls take() or read() while max_samples (in the ResourceLimitsQosPolicy ) is LENGTH_UNLIMITED (the default), and, the available data is greater than max_samples_per_read (in the DataReaderResourceLimitsQosPolicy ...
2975 reads — 0 comments
Note: Applies to RTI Connext 4.2 and above To prevent deadlocks, RTI uses mutexes to coordinate access to critical data and operations between threads. Mutexes are grouped in Exclusive Areas (EAs) code based on the regions they protect. However, deadlocks are still possible if you try to use ...
5184 reads — 0 comments

Pages