[
https://issues.apache.org/jira/browse/CAMEL-19032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688339#comment-17688339
]
Zheng Feng commented on CAMEL-19032:
------------------------------------
I also recommend to use LRASagaService and narayana-lra-coordinator. Please
check [MicroProfile LRA
Spec|https://download.eclipse.org/microprofile/microprofile-lra-1.0/microprofile-lra-spec-1.0.html#timing-out-lras-and-compensators]
for the timeout handling. And yeah, the doc should be improved. Do you like to
contribute with a docoment fix? [~chen19980]
> saga timeout value isn't depends on the min of the all participants like
> official doc described.
> ------------------------------------------------------------------------------------------------
>
> Key: CAMEL-19032
> URL: https://issues.apache.org/jira/browse/CAMEL-19032
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 3.19.0
> Reporter: adam chen
> Priority: Major
> Attachments: 2023-02-01-13-57-16.jpg, RouteCode.jpg
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> In my test result isn't like offical explanation (All participants (e.g.
> credit service, order service) can set their own timeout. The minimum value
> of those timeouts is taken as timeout for the saga when they are composed
> together.) In my result show that saga timeut value is depending on first
> participant's timeout value, not the minimum vlaue of participants. [Test
> code|https://github.com/chen19980/SAGA_timeout_test]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
