From 009cda47d0b4a9c145d0a443b60c483db06b2923 Mon Sep 17 00:00:00 2001 From: Wim De Troyer <58472100+wimdetroyer@users.noreply.github.com> Date: Fri, 4 Oct 2024 15:58:30 +0200 Subject: [PATCH] Update distributed-locks.adoc fix two typos --- .../antora/modules/ROOT/pages/distributed-locks.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/reference/antora/modules/ROOT/pages/distributed-locks.adoc b/src/reference/antora/modules/ROOT/pages/distributed-locks.adoc index c4266b7b6b4..09d9022e3ab 100644 --- a/src/reference/antora/modules/ROOT/pages/distributed-locks.adoc +++ b/src/reference/antora/modules/ROOT/pages/distributed-locks.adoc @@ -8,7 +8,7 @@ However, the problem becomes more complex when an application is distributed and The locking in this case is challenging and requires some shared state and its specific approach to achieve the exclusivity requirement. Spring Integration provides a `LockRegistry` abstraction with an in-memory `DefaultLockRegistry` implementation based on the `ReentrantLock` API. -The `obtain(Object)` method of the `LockRegistrty` requires a `lock key` for specific context. +The `obtain(Object)` method of the `LockRegistry` requires a `lock key` for specific context. For example, an aggregator uses a `correlationKey` to lock operations around its group. This way different locks can be used concurrently. This `obtain(Object)` method returns a `java.util.concurrent.locks.Lock` instance (depending on the `LockRegistry` implementation), therefore the rest of the logic is the same as standard Java Concurrency algorithm. @@ -27,11 +27,11 @@ registry.executeLocked("someLockKey", () -> someExclusiveResourceCall()); The method rethrows an exception from the task call, throws an `InterruptedException` if `Lock` is interrupted. In addition, a variant with `Duration` throws a `java.util.concurrent.TimeoutException` when `lock.tryLock()` returns `false`. -Spring Integration provides these `LockRegistrty` implementations for distributed locks: +Spring Integration provides these `LockRegistry` implementations for distributed locks: * xref:hazelcast.adoc#hazelcast-lock-registry[Hazelcast] * xref:jdbc/lock-registry.adoc[JDBC] * xref:redis.adoc#redis-lock-registry[Redis] * xref:zookeeper.adoc#zk-lock-registry[Zookeeper] -https://github.com/spring-projects/spring-integration-aws[Spring Integration AWS] extension also implements a `DynamoDbLockRegistry`. \ No newline at end of file +https://github.com/spring-projects/spring-integration-aws[Spring Integration AWS] extension also implements a `DynamoDbLockRegistry`.