You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/reference/antora/modules/ROOT/pages/jdbc/lock-registry.adoc
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -43,12 +43,12 @@ So the time to live can be highly reduce and deployments can retake a lost lock
43
43
44
44
NOTE: The lock renewal can be done only if the lock is held by the current thread.
45
45
46
-
String with version 5.5.6, the `JdbcLockRegistry` is support automatically clean up cache for JdbcLock in `JdbcLockRegistry.locks` via `JdbcLockRegistry.setCacheCapacity()`.
46
+
Starting with version 5.5.6, the `JdbcLockRegistry` is support automatically clean up cache for JdbcLock in `JdbcLockRegistry.locks` via `JdbcLockRegistry.setCacheCapacity()`.
47
47
See its JavaDocs for more information.
48
48
49
-
String with version 6.0, the `DefaultLockRepository` can be supplied with a `PlatformTransactionManager` instead of relying on the primary bean from the application context.
49
+
Starting with version 6.0, the `DefaultLockRepository` can be supplied with a `PlatformTransactionManager` instead of relying on the primary bean from the application context.
50
50
51
-
String with version 6.1, the `DefaultLockRepository` can be configured for custom `insert`, `update` and `renew` queries.
51
+
Starting with version 6.1, the `DefaultLockRepository` can be configured for custom `insert`, `update` and `renew` queries.
52
52
For this purpose the respective setters and getters are exposed.
53
53
For example, an insert query for PostgreSQL hint can be configured like this:
Copy file name to clipboardExpand all lines: src/reference/antora/modules/ROOT/pages/redis.adoc
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -643,7 +643,7 @@ For more information about commands, their arguments and result type, see https:
643
643
== Redis Queue Outbound Gateway
644
644
645
645
Spring Integration introduced the Redis queue outbound gateway to perform request and reply scenarios.
646
-
It pushes a conversation `UUID` to the provided `queue`, pushes the value with that `UUID` as its key to a Redis list, and waits for the reply from a Redis list with a key of `UUID' plus '.reply`.
646
+
It pushes a conversation `UUID` to the provided `queue`, pushes the value with that `UUID` as its key to a Redis list, and waits for the reply from a Redis list with a key of `UUID` plus `.reply`.
647
647
A different UUID is used for each interaction.
648
648
The following listing shows the available attributes for a Redis outbound gateway:
649
649
@@ -844,10 +844,10 @@ You should set the expiry at a large enough value to prevent this condition, but
844
844
845
845
Starting with version 5.0, the `RedisLockRegistry` implements `ExpirableLockRegistry`, which removes locks last acquired more than `age` ago and that are not currently locked.
846
846
847
-
String with version 5.5.6, the `RedisLockRegistry` is support automatically clean up cache for redisLocks in `RedisLockRegistry.locks` via `RedisLockRegistry.setCacheCapacity()`.
847
+
Starting with version 5.5.6, the `RedisLockRegistry` is support automatically clean up cache for redisLocks in `RedisLockRegistry.locks` via `RedisLockRegistry.setCacheCapacity()`.
848
848
See its JavaDocs for more information.
849
849
850
-
String with version 5.5.13, the `RedisLockRegistry` exposes a `setRedisLockType(RedisLockType)` option to determine in which mode a Redis lock acquisition should happen:
850
+
Starting with version 5.5.13, the `RedisLockRegistry` exposes a `setRedisLockType(RedisLockType)` option to determine in which mode a Redis lock acquisition should happen:
851
851
852
852
- `RedisLockType.SPIN_LOCK` - the lock is acquired by periodic loop (100ms) checking whether the lock can be acquired.
Copy file name to clipboardExpand all lines: src/reference/antora/modules/ROOT/pages/zookeeper.adoc
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ public interface KeyToPathStrategy {
81
81
If the strategy returns `true` from `isBounded`, unused locks do not need to be harvested.
82
82
For unbounded strategies (such as the default), you need to periodically invoke `expireUnusedOlderThan(long age)` to remove old unused locks from memory.
83
83
84
-
String with version 5.5.6, the `ZookeeperLockRegistry` is support automatically clean up cache for ZkLock in `ZookeeperLockRegistry.locks` via `ZookeeperLockRegistry.setCacheCapacity()`.
84
+
Starting with version 5.5.6, the `ZookeeperLockRegistry` is support automatically clean up cache for ZkLock in `ZookeeperLockRegistry.locks` via `ZookeeperLockRegistry.setCacheCapacity()`.
0 commit comments