[
https://issues.apache.org/jira/browse/CAMEL-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072566#comment-18072566
]
Roman Stechkevych commented on CAMEL-23294:
-------------------------------------------
Thanks [~fmariani] for the update. My github username is stechrom.
> [camel-sql] JDBC-based Idempotent repository strategy fails in racing
> conditions.
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-23294
> URL: https://issues.apache.org/jira/browse/CAMEL-23294
> Project: Camel
> Issue Type: Bug
> Components: camel-sql
> Affects Versions: 4.14.5
> Reporter: Roman Stechkevych
> Assignee: Federico Mariani
> Priority: Major
> Fix For: 4.14.6, 4.18.2, 4.19.0
>
> Attachments: AbstractJdbcMessageIdRepository_patched.png,
> JdbcOrphanLockAwareIdempotentRepository_patched.png
>
>
> Issue occurs when JDBC-based idempotent repository is used by multiple
> applications (instances), which are processing concurrently big number of
> files, for example.
> In my particular use case readLock=idempotent is configured for Camel File
> component endpoint. As a result, read lock can be acquired by two instances
> at the same time, which leads to unwanted simultaneous file processing.
> Issue is reproducible during concurrency test with 200 files being processed
> by two instances of the same application using JDBC-based idempotent
> repository.
> After corresponding fix (please find in attachments), issue has been resolved.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
