You are here: Part 2: Core Concepts > DDS Entities > QosPolicies


Connext DDS’s behavior is controlled by the Quality of Service (QoS) policies of the data communication Entities (DomainParticipant, Topic, Publisher, Subscriber, DataWriter, and DataReader) used in your applications. This section summarizes each of the QosPolicies that you can set for the various Entities.

The QosPolicy class is the abstract base class for all the QosPolicies. It provides the basic mechanism for an application to specify quality of service parameters. lists each supported QosPolicy (in alphabetical order), provides a summary, and points to a section in the manual that provides further details.

The detailed description of a QosPolicy that applies to multiple Entities is provided in the first chapter that discusses an Entity whose behavior the QoS affects. Otherwise, the discussion of a QosPolicy can be found in the chapter of the particular Entity to which the policy applies. As you will see in the detailed description sections, all QosPolicies have one or more parameters that are used to configure the policy. The how’s and why’s of tuning the parameters are also discussed in those sections.

As first discussed in Controlling Behavior with Quality of Service (QoS) Policies, QosPolicies may interact with each other, and certain values of QosPolicies can be incompatible with the values set for other policies.

The set_qos() operation will fail if you attempt to specify a set of values would result in an inconsistent set of policies. To indicate a failure, set_qos() will return INCONSISTENT_POLICY. QoS Requested vs. Offered Compatibility—the RxO Property provides further information on QoS compatibility within an Entity as well as across matching Entities, as does the discussion/reference section for each QosPolicy listed in .

The values of some QosPolicies cannot be changed after the Entity is created or after the Entity is enabled. Others may be changed at any time. The detailed section on each QosPolicy states when each policy can be changed. If you attempt to change a QosPolicy after it becomes immutable (because the associated Entity has been created or enabled, depending on the policy), set_qos() will fail with a return code of IMMUTABLE_POLICY.





Configures the mechanism that sends user data in an external middleware thread. See ASYNCHRONOUS_PUBLISHER QosPolicy (DDS Extension).


This QoS policy is used in the context of two features:

For a Collaborative DataWriter, specifies the group of DataWriters expected to collaboratively provide data and the timeouts that control when to allow data to be available that may skip DDS samples.

For a Durable Subscription, configures a set of Durable Subscriptions on a DataWriter.

See AVAILABILITY QosPolicy (DDS Extension).


Specifies and configures the mechanism that allows Connext DDS to collect multiple DDS data samples to be sent in a single network packet, to take advantage of the efficiency of sending larger packets and thus increase effective throughput. See BATCH QosPolicy (DDS Extension).


Various settings and resource limits used by Connext DDS to control its internal database. See DATABASE QosPolicy (DDS Extension).


This QosPolicy configures the Connext DDS on-the-network protocol, RTPS. See DATA_READER_PROTOCOL QosPolicy (DDS Extension).


Various settings that configure how DataReaders allocate and use physical memory for internal resources. See DATA_READER_RESOURCE_LIMITS QosPolicy (DDS Extension).


This QosPolicy configures the Connext DDS on-the-network protocol, RTPS. See DATA_WRITER_PROTOCOL QosPolicy (DDS Extension).


Controls how many threads can concurrently block on a write() call of this DataWriter. Also controls the number of batches managed by the DataWriter and the instance-replacement kind used by the DataWriter. See DATA_WRITER_RESOURCE_LIMITS QosPolicy (DDS Extension).


For a DataReader, specifies the maximum expected elapsed time between arriving DDS data samples.

For a DataWriter, specifies a commitment to publish DDS samples with no greater elapsed time between them.

See DEADLINE QosPolicy.


Controls how Connext DDS will deal with data sent by multiple DataWriters for the same topic. Can be set to "by reception timestamp" or to "by source timestamp." See DESTINATION_ORDER QosPolicy.


Configures the mechanism used by Connext DDS to automatically discover and connect with new remote applications. See DISCOVERY QosPolicy (DDS Extension).


Controls the amount of delay in discovering Entities in the system and the amount of discovery traffic in the network. See DISCOVERY_CONFIG QosPolicy (DDS Extension).


Various settings that configure how DomainParticipants allocate and use physical memory for internal resources, including the maximum sizes of various properties. See DOMAIN_PARTICIPANT_RESOURCE_LIMITS QosPolicy (DDS Extension).


Specifies whether or not Connext DDS will store and deliver data that were previously published to new DataReaders. See DURABILITY QosPolicy.


Various settings to configure the external Persistence Service used by Connext DDS for DataWriters with a Durability QoS setting of Persistent Durability. See DURABILITY SERVICE QosPolicy.


Controls whether or not child Entities are created in the enabled state. See ENTITYFACTORY QosPolicy.


Assigns a name and role_name to an Entity. See ENTITY_NAME QosPolicy (DDS Extension).


Configures the DomainParticipant’s internal thread that handles timed events. See EVENT QosPolicy (DDS Extension).


Configures multi-thread concurrency and deadlock prevention capabilities. See EXCLUSIVE_AREA QosPolicy (DDS Extension).


Along with TOPIC_DATA QosPolicy and USER_DATA QosPolicy, this QosPolicy is used to attach a buffer of bytes to Connext DDS's discovery meta-data. See GROUP_DATA QosPolicy.


Specifies how much data must be stored by Connext DDS for the DataWriter or DataReader. This QosPolicy affects the RELIABILITY QosPolicy as well as the DURABILITY QosPolicy. See HISTORY QosPolicy.


Suggestion to Connext DDS on how much time is allowed to deliver data. See LATENCYBUDGET QoS Policy.


Specifies how long Connext DDS should consider data sent by an user application to be valid. See LIFESPAN QoS Policy.


Specifies and configures the mechanism that allows DataReaders to detect when DataWriters become disconnected or "dead." See LIVELINESS QosPolicy.


Configures the properties associated with Connext DDS logging. See LOGGING QosPolicy (DDS Extension).


Configures a DataWriter’s ability to send data on different multicast groups (addresses) based on the value of the data. See MULTI_CHANNEL QosPolicy (DDS Extension).


Along with Ownership Strength, specifies if DataReaders for a topic can receive data from multiple DataWriters at the same time. See OWNERSHIP QosPolicy.


Used to arbitrate among multiple DataWriters of the same instance of a Topic when Ownership QoSPolicy is EXLUSIVE. See OWNERSHIP_STRENGTH QosPolicy.


Adds string identifiers that are used for matching DataReaders and DataWriters for the same Topic. See PARTITION QosPolicy.


Controls how Connext DDS presents data received by an application to the DataReaders of the data. See PRESENTATION QosPolicy.


Configures the way that XML documents containing QoS profiles are loaded by RTI. See PROFILE QosPolicy (DDS Extension) .


Stores name/value(string) pairs that can be used to configure certain parameters of Connext DDS that are not exposed through formal QoS policies. It can also be used to store and propagate application-specific name/value pairs, which can be retrieved by user code during discovery. See PROPERTY QosPolicy (DDS Extension) .


Specifies how Connext DDS sends application data on the network. By default, data is sent in the user thread that calls the DataWriter’s write() operation. However, this QosPolicy can be used to tell Connext DDS to use its own thread to send the data. See PUBLISH_MODE QosPolicy (DDS Extension).


Controls how a DataReader manages the lifecycle of the data that it has received. See READER_DATA_LIFECYCLE QoS Policy.


Configures threads used by Connext DDS to receive and process data from transports (for example, UDP sockets). See RECEIVER_POOL QosPolicy (DDS Extension).


Specifies whether or not Connext DDS will deliver data reliably. See RELIABILITY QosPolicy.


Controls the amount of physical memory allocated for Entities, if dynamic allocations are allowed, and how they occur. Also controls memory usage among different instance values for keyed topics. See RESOURCE_LIMITS QosPolicy.


Intended for use by RTI infrastructure services. User applications should not modify its value. See SERVICE QosPolicy (DDS Extension).


Configures DomainParticipant-independent resources used by Connext DDS. Mainly used to change the maximum number of DomainParticipants that can be created within a single process (address space). See SYSTEM_RESOURCE_LIMITS QoS Policy (DDS Extension).


Set by a DataReader to limit the number of new data values received over a period of time. See TIME_BASED_FILTER QosPolicy.


Along with Group Data QosPolicy and User Data QosPolicy, used to attach a buffer of bytes to Connext DDS's discovery meta-data. See TOPIC_DATA QosPolicy.


Specifies which built-in transport plugins are used. See TRANSPORT_BUILTIN QosPolicy (DDS Extension).


Specifies the multicast address on which a DataReader wants to receive its data. Can specify a port number as well as a subset of the available transports with which to receive the multicast data. See TRANSPORT_MULTICAST QosPolicy (DDS Extension).


Specifies the automatic mapping between a list of topic expressions and multicast address that can be used by a DataReader to receive data for a specific topic. See TRANSPORT_MULTICAST_MAPPING QosPolicy (DDS Extension).


Set by a DataWriter or DataReader to tell Connext DDS that the data being sent is a different "priority" than other data. See TRANSPORT_PRIORITY QosPolicy.


Allows you to select which physical transports a DataWriter or DataReader may use to send or receive its data. See TRANSPORT_SELECTION QosPolicy (DDS Extension).


Specifies a subset of transports and port number that can be used by an Entity to receive data. See TRANSPORT_UNICAST QosPolicy (DDS Extension).


Defines rules that determine whether the type used to publish a given data stream is consistent with that used to subscribe to it. See TYPE_CONSISTENCY_ENFORCEMENT QosPolicy.


Used to attach application-specific value(s) to a DataWriter or DataReader. These values are passed to the serialization or deserialization routine of the associated data type. Also controls whether padding bytes are set to 0 during serialization. See TYPESUPPORT QosPolicy (DDS Extension).


Along with Topic Data QosPolicy and Group Data QosPolicy, used to attach a buffer of bytes to Connext DDS's discovery meta-data. See USER_DATA QosPolicy.


Specifies IDs used by the RTPS wire protocol to create globally unique identifiers. See WIRE_PROTOCOL QosPolicy (DDS Extension).


Controls how a DataWriter handles the lifecycle of the instances (keys) that the DataWriter is registered to manage. See WRITER_DATA_LIFECYCLE QoS Policy.

© 2016 RTI