6.6.5. Fixes Related to Group Presentation
6.6.5.1. [Critical] Application may not have received samples of coherent set when using GROUP access scope and TRANSIENT_LOCAL durability
An application using GROUP access scope and TRANSIENT_LOCAL (or higher) durability may not have received the samples for some coherent sets, or it may have received the samples with delay.
Assume a coherent set ‘CS1’ published by a set of DataWriters that are part of the same group. This coherent set was not provided to the application if all the following conditions were true:
The DataReaders receiving ‘CS1’ matched with the DataWriters publishing ‘CS1’ after the coherent set was published.
‘CS1’ did not contain samples for some of the DataWriters in the group, or the samples were removed after applying the Lifespan QoS Policy. If ‘CS1’ contained at least one sample per DataWriter in the group, this problem did not occur.
The application did not publish a new coherent set after ‘CS1’; or, if it did, the new coherent set did not contain samples from at least one of the DataWriters that were missing samples from ‘CS1’.
If the third condition was not met, then the delivery of the coherent set would be delayed instead of the coherent set not being provided.
[RTI Issue ID CORE-12350]
6.6.5.2. [Critical] Segmentation fault when using GROUP_PRESENTATION_QOS or HIGHEST_OFFERED_PRESENTATION_QOS and setting filter_redundant_samples to FALSE on DataReader
An application generated a segmentation fault if it created a DataReader with the following valid configuration:
subscriber_qos.presentation.access_scope = DDS_GROUP_PRESENTATION_QOS or DDS_HIGHEST_OFFERED_PRESENTATION_QOS
datareader_qos.availability.max_data_availability_waiting_time = DDS_DURATION_ZERO
datareader_qos.availability.max_endpoint_availability_waiting_time = DDS_DURATION_ZERO
datareader_qos.property contained dds.data_reader.state.filter_redundant_samples with the value “false”
This problem has been resolved by allowing the DataReader to be created.
[RTI Issue ID CORE-12771]
6.6.5.3. [Major] Application may stop receiving samples from DataReaders using GROUP_PRESENTATION_QOS
An application may have stopped receiving samples from DataReaders that were part of a Subscriber using GROUP_PRESENTATION_QOS under the following scenario:
The Publisher’s group contained at least one keyed DataWriter and one unkeyed DataWriter.
The Subscriber’s group contained only keyed DataReaders or unkeyed DataReaders, but not both.
This problem has been resolved.
[RTI Issue ID CORE-12161]