Hi,
I have an application that is subscribing to data on a specific instance. Code to do this works fine, as per the RTI worked examples:
dds::sub::LoanedSamples<DataType> samples = reader.select().max_samples(1).instance(instance_handle).read();
for (const auto& sample : samples) {
if (sample.info().valid()) {
std::cout << "Subscribed to InstanceID: " << sample.data().InstanceID() << std::endl;
DataType dataOut = sample.data();
}
}
Hi, currently i am exploring a few options to retrieve data from the datareader.
I am looking at using Waitset with infinite timeout.
As i will have a lot of datareaders, therefore i will have a lot of threads using the Waitset to wait for data.
1) Can i find out when i use Waitset wait() with infinite timeout, is the thread put to sleep?
2) Will there still be any CPU utilization during the wait(), as in will the thread wakes up periodically to check if the Status Condition is triggered?
Thanks.
While using the traditional C++ API, is the WaitSet vulnerable to spurious wakeups?
The traditional C++ API documentation does not seem to address this, but the modern C++ API however, has an additional class called AsyncWaitSet. A quote from it's documentation:
I am writing a (modern C++) module to simulate a device that connects to a central registry to send and obtain information. The registry and device each pass data both ways, so act as both subscribers and publishers.
Hello,
Many applcations in our system use WaitSets to detect various DDS conditions, and react accordingly. At this stage, most, if not all, use a single WaitSet.
Are there any performance issues that one should be aware of before introducing a second WaitSet, with a different set of conditions attached, into an application?
My initial guess is that the extra WaitSet would mean at least one extra thread in the application. But is there anything else?
Thanks in advance
Dallas
I have a publisher/subscriber pair (created using DDSTheParticipantFactory->create_participant_from_config). The subscriber uses a dynamic reader and waits on DDS_DATA_AVAILABLE_STATUS to receive new data from the publisher. At publication rates of > around 5 Hz, the subscriber begins to "miss" new samples, getting worse as the publication rate is increased. It will typically go for 1 - 3 seconds without seeing new samples, then receive a short burst (2 - 10) of consecutive samples, and repeat this cycle.
Hello,
I'm encountering the following unhandled exception in nddsdotnet40.dll when my application shuts down:
System.AccessViolationException was unhandled
HResult=-2147467261
Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Source=nddsdotnet40
StackTrace:
at DDS.WaitSet.!WaitSet()
at DDS.WaitSet.Dispose(Boolean )
at DDS.WaitSet.Finalize()
InnerException:
I've traced through all my Dispose() methods and it doesn't seem that anything is directly causing this exception.
