CAMEL-23294: fix orphan lock race in JDBC idempotent repository (4.18.x)#22518
Merged
davsclaus merged 1 commit intoapache:camel-4.18.xfrom Apr 10, 2026
Merged
Conversation
When multiple instances concurrently recover the same orphan lock, both succeed because add() ignores insert()'s return value and insert() updates the timestamp unconditionally. Fix: - add() now checks insert()'s return value (0 = not acquired) - insert() uses conditional UPDATE (WHERE createdAt < ?) for orphan recovery so only one instance can claim an orphan lock
oscerd
approved these changes
Apr 9, 2026
davsclaus
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Claude Code on behalf of Federico Mariani
Backport of #22515 to
camel-4.18.x.Fixes a race condition in
JdbcOrphanLockAwareIdempotentRepositorywhere multiple instances can simultaneously acquire the same orphan lock, causing duplicate file processing withreadLock=idempotent.add()now checksinsert()'s return valueinsert()uses conditionalUPDATE ... WHERE createdAt < ?for orphan recoveryTest plan