From 7ca2b138ca362e5ccb962a1b3e0ea7cc85f71d0f Mon Sep 17 00:00:00 2001 From: FrancescoFioraEst Date: Mon, 19 May 2025 13:59:39 +0100 Subject: [PATCH] Update docs for new parameter for timeout in ACM runtime Issue-ID: POLICY-5371 Change-Id: I7e69d8727522826fe8c7ed236a5f4027df003c7c Signed-off-by: FrancescoFioraEst --- docs/clamp/acm/api-protocol/system-level-dialogues.rst | 3 ++- docs/development/devtools/smoke/files/runtime-application.yaml | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/clamp/acm/api-protocol/system-level-dialogues.rst b/docs/clamp/acm/api-protocol/system-level-dialogues.rst index 0f0c0e7d..b7a05cc2 100644 --- a/docs/clamp/acm/api-protocol/system-level-dialogues.rst +++ b/docs/clamp/acm/api-protocol/system-level-dialogues.rst @@ -298,13 +298,14 @@ the operation result is then marked as 'TIMEOUT' by the ACM-R after the configur .. image:: ../images/system-dialogues/TimeoutAcmResult.png -The following parameter is set in the application properties for the runtime to configure the 'TIMEOUT' value in milliseconds. +The following parameters are set in the application properties for the runtime to configure the 'TIMEOUT' value in milliseconds. .. code-block:: yaml runtime: participantParameters: maxStatusWaitMs: 100000 --> Denotes the maximum wait time by the runtime to receive the periodic status update from the participants + maxOperationWaitMs: 100000 --> Denotes the maximum wait time by the runtime to receive the state change update from the participants An ACM operation has to be completed and updated with any of the above specified result values in order to allow the user to trigger subsequent requests. The user cannot trigger any state change events before the operation gets completed. When an operation is marked 'TIMEOUT', the following scenarios are applicable. diff --git a/docs/development/devtools/smoke/files/runtime-application.yaml b/docs/development/devtools/smoke/files/runtime-application.yaml index d9639226..d30107ab 100644 --- a/docs/development/devtools/smoke/files/runtime-application.yaml +++ b/docs/development/devtools/smoke/files/runtime-application.yaml @@ -5,7 +5,8 @@ runtime: syncTopic: acm-ppnt-sync participantParameters: heartBeatMs: 20000 - maxStatusWaitMs: 200000 + maxStatusWaitMs: 150000 + maxOperationWaitMs: 200000 topicParameterGroup: topicSources: - topic: ${runtime.topics.operationTopic} -- 2.16.6