RTI Connext Java API Version 7.7.0

<<extension>> Specifies a subset of transports and a port number that can be used by an Entity to receive data. More...

Inheritance diagram for TransportUnicastQosPolicy:
QosPolicy

Public Attributes

final TransportUnicastSettingsSeq value
 <<extension>> A sequence of unicast communication settings. More...
 
- Public Attributes inherited from QosPolicy
final QosPolicyId_t id
 The ID of this QoS policy. More...
 
final String policy_name
 The name of this QoS policy. More...
 

Detailed Description

<<extension>> Specifies a subset of transports and a port number that can be used by an Entity to receive data.

Entity:
com.rti.dds.domain.DomainParticipant, com.rti.dds.subscription.DataReader, com.rti.dds.publication.DataWriter
Properties:
RxO = N/A
Changeable = NO

Usage

RTI Connext may send data to a variety of Entities, not just DataReaders. For example, reliable DataWriters may receive ACK/NACK packets from reliable DataReaders.

During discovery, each com.rti.dds.infrastructure.Entity announces to remote applications a list of (up to 16) unicast addresses to which the remote application should send data (either user data packets or reliable protocol meta-data such as ACK/NACKs and heartbeats). Note that this is a hard limit that cannot be increased. However, this limit can be decreased by configuring the 'dds.domain_participant.max_announced_locator_list_size' property in the com.rti.dds.infrastructure.PropertyQosPolicy associated with the com.rti.dds.domain.DomainParticipantQos.

Note: RTI Connext internally uses several dynamic locator lists to keep track of configured unicast locators. The initial size of these lists can be configured with the com.rti.dds.domain.DomainParticipant property 'dds.domain_participant.initial_locator_list_size'. By default, the initial size is derived from local information, such as the number of local locators. To prevent dynamic resizing at runtime, set the property's value to the maximum number of locators that a single participant or endpoint may advertise at any given time in your system.

By default, the list of addresses is populated automatically with values obtained from the enabled transport plug-ins allowed to be used by the Entity (see com.rti.dds.infrastructure.TransportBuiltinQosPolicy and com.rti.dds.infrastructure.TransportSelectionQosPolicy). Also, the associated ports are automatically determined (see com.rti.dds.infrastructure.RtpsWellKnownPorts_t).

Use this QoS policy to manually set the receive address list for an Entity. You may optionally set a port to use a non-default receive port as well. Only the first 16 addresses will be used.

RTI Connext will create a receive thread for every unique port number that it encounters (on a per transport basis).

Member Data Documentation

◆ value

<<extension>> A sequence of unicast communication settings.

An empty sequence means that applicable defaults specified by elsewhere (e.g. com.rti.dds.domain.DomainParticipantQos.default_unicast) should be used.

The RTPS wire protocol currently limits the maximum number of unicast locators to

  1. Note that this is a hard limit that cannot be increased. However, this limit can be decreased by configuring the 'dds.domain_participant.max_announced_locator_list_size' property in the com.rti.dds.infrastructure.PropertyQosPolicy associated with the com.rti.dds.domain.DomainParticipantQos.

[default] Empty sequence.

See also
com.rti.dds.domain.DomainParticipantQos.default_unicast
Categories
Immutable, Transports, Discovery Metadata