[ 
https://issues.apache.org/jira/browse/CAMEL-23352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-23352.
---------------------------------
    Resolution: Fixed

> AggregateProcessor: Add configuration option for synchronous Optimistic 
> Locking retry behavior
> ----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23352
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23352
>             Project: Camel
>          Issue Type: Improvement
>          Components: came-core
>    Affects Versions: 3.22.4, 4.x
>            Reporter: Marcel
>            Priority: Minor
>              Labels: aggregator
>             Fix For: 4.21.0
>
>
> Currently the AggregateProcessor performs Optimistic Locking retries 
> asynchronously
> in a separate thread (behavior introduced in Camel 3.x). In Camel 2.x the 
> retries
> were synchronous.
> This change broke use cases where the aggregator is used together with a 
> persistent
> aggregation repository inside a transaction. In such setups, a synchronous 
> answer
> from the aggregator is required to decide whether to commit or roll back the
> currently open transaction.
> We propose adding a configuration flag to AggregateProcessor (e.g.
> optimisticLockingSynchronous=true/false) to allow users to choose between
> synchronous and asynchronous Optimistic Locking retry behavior.
> We are prepared to provide a PR implementing this option.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to