From 48bd9615c7a74c37e800d2dbb04b1bbc4f2ad896 Mon Sep 17 00:00:00 2001 From: JesusPoderoso Date: Mon, 13 May 2024 16:04:20 +0200 Subject: [PATCH] Refs #20934: Apply internal rev suggestions Signed-off-by: JesusPoderoso --- .../dds_layer/core/policy/eprosimaExtensions.rst | 7 ++++--- docs/fastdds/transport/listening_locators.rst | 10 +++++----- 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/fastdds/dds_layer/core/policy/eprosimaExtensions.rst b/docs/fastdds/dds_layer/core/policy/eprosimaExtensions.rst index 4d400b0e3..66598ceab 100644 --- a/docs/fastdds/dds_layer/core/policy/eprosimaExtensions.rst +++ b/docs/fastdds/dds_layer/core/policy/eprosimaExtensions.rst @@ -1244,9 +1244,10 @@ List of QoS Policy data members: :ref:`DS_modify_server_list`). .. note:: - In single process deployments where multiple endpoints are created within the same DomainParticipant, each of - them will have the same **participantId** but different *unicast locator* ports. - That can lead on participant creation failure if the amount of endpoints to be created reaches the value of + In single process deployments where multiple Datareaders and Datawriters are created within the same + DomainParticipant, each of them will have the same **participantId** but different *unicast locator* ports. + That can lead on participant creation failure if the amount of Datareaders and Datawriters to be created reaches + the value of :cpp:var:`BuiltinAttributes::mutation_tries`, due to exceeding the maximum amount of mutations of the same **participantId** into different port number for the *unicast locator* creation. diff --git a/docs/fastdds/transport/listening_locators.rst b/docs/fastdds/transport/listening_locators.rst index 879e70b0d..7a2ae1aa3 100644 --- a/docs/fastdds/transport/listening_locators.rst +++ b/docs/fastdds/transport/listening_locators.rst @@ -218,11 +218,11 @@ The default values can be modified using the |WireProtocolConfigQos::port-api| m .. note:: - In single process deployments where multiple endpoints are created within the same DomainParticipant, each of - them will have the same **participantId** but different *unicast locator* ports. - That can lead on participant creation failure if the amount of endpoints to be created reaches the value of - :cpp:var:`mutation_tries`, due to exceeding the - maximum amount of mutations of the same **participantId** into different port number for the *unicast locator* + In single process deployments where multiple Datareaders and Datawriters are created within the same + DomainParticipant, each of them will have the same **participantId** but different *unicast locator* ports. + That can lead on participant creation failure if the amount of Datareaders and Datawriters to be created reaches the + value of :cpp:var:`mutation_tries`, due to exceeding + the maximum amount of mutations of the same **participantId** into different port number for the *unicast locator* creation. Refer to :ref:`this example ` for configuring both the **participantId** and the