This is an automated email from the ASF dual-hosted git repository. Croway pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1e3f89e2c6969d9aad664c42aeabfff71dbdd3a5 Author: Croway <[email protected]> AuthorDate: Mon Jun 8 18:08:55 2026 +0200 CAMEL-23714: Add upgrade guide entry for RedisAggregationRepository changes --- .../modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc index b02c23dcc37a..1f3a32cd01bf 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc @@ -389,6 +389,17 @@ sjms:queue:foo?objectMessageEnabled=true sjms2:queue:foo?objectMessageEnabled=true ---- +=== camel-redis + +The `RedisAggregationRepository` now uses per-key distributed locks instead of a single global lock. +Previously, all pessimistic aggregation operations serialized on a single Redis lock named `"aggregationLock"`. +The lock key is now `<mapName>-lock-<correlationKey>`, so operations on unrelated correlation keys no longer +block each other. Existing deployments that inspect Redis lock keys will see different key names after upgrading. + +The `remove()` method now throws `RuntimeCamelException` instead of `RuntimeException` when a transaction +rollback occurs. Routes that catch `RuntimeException` explicitly are unaffected, but routes that catch +`RuntimeCamelException` specifically will now also catch this failure path. + === camel-hazelcast Hazelcast instances created and managed by Camel (when no user-supplied
