Fix LockRegistrty typo in the distributed-locks.adoc
This commit is contained in:
@@ -7,7 +7,7 @@ For this purpose Java provides an API with `java.util.concurrent.locks.Lock` imp
|
||||
However, the problem becomes more complex when an application is distributed and/or run in the cluster.
|
||||
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 `LockRegistrty` abstraction with an in-memory `DefaultLockRegistry` implementation based on the `ReentrantLock` API.
|
||||
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.
|
||||
For example, an aggregator uses a `correlationKey` to lock operations around its group.
|
||||
This way different locks can be used concurrently.
|
||||
|
||||
Reference in New Issue
Block a user