From d962dec95472482eb150cc3acef09ddc1ae0bc53 Mon Sep 17 00:00:00 2001 From: vramik Date: Mon, 3 Apr 2023 12:42:46 +0200 Subject: [PATCH] Remove workaround for Lazy initialization of Realm's collections Closes #19069 --- .../main/java/org/keycloak/models/jpa/JpaRealmProvider.java | 6 ------ 1 file changed, 6 deletions(-) diff --git a/model/jpa/src/main/java/org/keycloak/models/jpa/JpaRealmProvider.java b/model/jpa/src/main/java/org/keycloak/models/jpa/JpaRealmProvider.java index b0077655aff..8b25b396fc3 100644 --- a/model/jpa/src/main/java/org/keycloak/models/jpa/JpaRealmProvider.java +++ b/model/jpa/src/main/java/org/keycloak/models/jpa/JpaRealmProvider.java @@ -166,12 +166,6 @@ public class JpaRealmProvider implements RealmProvider, ClientProvider, ClientSc if (realm == null) { return false; } - - // Workaround tracked by issue https://github.com/keycloak/keycloak/pull/19069 - // As of Hibernate 6.2.0.CR3, after the em.refresh(entity) the lazily loaded collections in realm don't load anymore, instead there is a - // LazyInitializationException. As a workaround, comment out the refresh call. - // em.refresh(realm); - final RealmAdapter adapter = new RealmAdapter(session, em, realm); session.users().preRemove(adapter);