Incompatible QoS running Recorder

5 posts / 0 new
Last post
Offline
Last seen: 1 week 6 days ago
Joined: 04/11/2025
Posts: 3
Incompatible QoS running Recorder

I am attempting to use the RTI Recording Service. I have defined a QoS override file with Ownership for DataReaders and DataWriters to be Exclusive. 

When running the Recording service with vebosity, it does appear to be reading the QoS file from the environment variable, however, I am constantly getting the following errors:

 

PRESPsService_isRemoteWriterLocalReaderCompatible: INCOMPATIBLE QOS | Ownership: writer (exclusive), reader (shared). 

 

Where is it inheriting the shared reader from? Can the recorder only be used when the rest of the application QoS Ownership is shared?

Howard's picture
Offline
Last seen: 2 days 12 hours ago
Joined: 11/29/2012
Posts: 635

You have to apply the QOS Profile with the EXCLUSIVE setting to the Topics that you want to record in the Recording Service XML file. 

RTI Recording Service (as well as any application using Connext DDS) will load external XML files as you configure it to (NDDS_QOS_PROFILES environment variables or via API configuration, etc).

But you have to configure the apps to use specific profiles to create the DDS Entities that it uses (DataReaders, DataWriters, Participants).

You cannot (and should not in best practice), rely on "overriding" the default QoS with a user-defined profile...apps may not use the default QOS when creating their entities...

Offline
Last seen: 1 week 6 days ago
Joined: 04/11/2025
Posts: 3

The topics, when viewed in admin console, are using the EXCLUSIVE setting for both Data Readers and Data Writers. 

I don't experience any issues until I start the recording tool, as it appears to be using SHARED for it's Data Readers even when pointing it to use the QoS profile that I have defined. 

Offline
Last seen: 1 week 6 days ago
Joined: 04/11/2025
Posts: 3

Running the Shapes Demo and pushing a square with Default settings but changing the Ownership to Exclusive gives me the same behavior. I've attached a log for review as well. 

The recording service documentation (https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/services/recording_service/recorder/record_troubleshooting.html) mentions this issue but does not state the specific resolution.

File Attachments: 
Howard's picture
Offline
Last seen: 2 days 12 hours ago
Joined: 11/29/2012
Posts: 635

Are you looking at the QoS of the DataReaders of the Recording Service in Admin Console?

In the future it would be easier if you attached the configuration file with which you started Recording Service, but from the log output, it seems that you've defined a QoS Profile called "AvnsilQosLibrary::AvnsilQosOverridesProfile" and have configured Recording Service to configure the QoS of the DomainParticipant.

        <domain_participant_qos base_name="AvnsilQosLibrary::AvnsilQosOverridesProfile"/>

However, you did not configure the Recording Service to modify the QoS of the DataReaders that it creates.  Please see this documentation: https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/services/recording_service/recorder/record_configuration.html#topic-group.