10.4.13. Instances

10.4.13.1. [Major] Possible failure to send dispose/unregister messages when using async publication

When using asynchronous publication, Connext Micro may have failed to send dispose or unregister messages.

[RTI Issue ID MICRO-12789]

10.4.13.2. [Minor] Instance state transition inconsistent with Connext Professional

If a DataWriter called dispose() for an instance that was already unregistered, a DataReader would propagate the DDS_NOT_ALIVE_DISPOSED_INSTANCE_STATE instance state even if the instance had not received any samples. This behavior was different from Connext Professional.

A new policy, DataReaderQos.protocol.propagate_dispose_of_unregistered_instances, has been added to control if the DataReader should propagate DDS_NOT_ALIVE_DISPOSED_INSTANCE_STATE, even when no samples have been received for the instance. When set to false, the behavior is identical to Connext Professional.

[RTI Issue ID MICRO-2346]