libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Use entity locking only for the map storage

Browse source 
This is a performance optimization that the new feature doesn't affect the old store.

Closes #20176
This commit is contained in:
Alexander Schwartz 2023-05-05 13:46:48 +02:00 committed by Michal Hajas
parent bd7f62acc3
commit 910021408e
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
server-spi-private/src/main/java/org/keycloak/utils/LockObjectsForModification.java
View file

@ -17,6 +17,7 @@
package org.keycloak.utils;
import org.keycloak.common.Profile;
import org.keycloak.models.KeycloakSession;
import org.keycloak.models.RealmModel;
import org.keycloak.models.UserSessionModel;
@ -71,6 +72,11 @@ public class LockObjectsForModification {
}
private static <V> V lockObjectsForModification(KeycloakSession session, Class<?> model, CallableWithoutThrowingAnException<V> callable) {
// Only map storage supports locking objects for modification, skip the logic if it is not enabled.
if (!Profile.isFeatureEnabled(Profile.Feature.MAP_STORAGE)) {
return callable.call();
}
if (LockObjectsForModification.isEnabled(session, model)) {
// If someone nests the call, and it would already be locked, don't try to lock it a second time.
// Otherwise, the inner unlocking might also unlock the outer lock.