Repository navigation
Keycloak Pod not coming up with DefaultCacheManager error #41784
Unanswered
nithinvithayathil
asked this question in
Q&A
Replies: 2 comments
|
Is there anything else that looks like a relevant exception in the logs? This error I belive is just a timing issue - the DefaultCacheManager is already shutting down. Also have you tried later keycloak versions? That may at least clarify the error. cc @pruivo |
0 replies
|
Without the full logs, it is impossible to tell. @nithinvithayathil Do you have them? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I had 2 pod instance of Keycloak version 24 running in my kubernetes cluster. During node maintenance the pods got restarted and one of the pod didnt come up. It was failing with the below error. This is the first such instance of keycloak pod not coming up.
2025-08-08 07:15:13,665 ERROR [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000660: DefaultCacheManager start failed, stopping any running components: java.lang.IllegalStateException: Shutdown in progress
at java.base/java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:66)
at java.base/java.lang.Runtime.addShutdownHook(Runtime.java:216)
at org.infinispan.factories.GlobalComponentRegistry.addShutdownHook(GlobalComponentRegistry.java:231)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:382)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:252)
at org.infinispan.manager.DefaultCacheManager.internalStart(DefaultCacheManager.java:779)
at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:747)
at org.infinispan.manager.DefaultCacheManager.(DefaultCacheManager.java:411)
at org.keycloak.quarkus.runtime.storage.legacy.infinispan.CacheManagerFactory.startCacheManager(CacheManagerFactory.java:116)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Restarting the pod did not help and it throws the same error. As it was a non production instance i had to finally redeploy it once again that fixed the issue for now. But trying to see if i can do something else different incase if this comes up in production.
Keycloak version - 24
Some of the relevant environment variables i have used in my deployment:
CACHE_OWNERS_AUTH_SESSIONS_COUNT : 2
CACHE_OWNERS_COUNT : 2
JGROUPS_DISCOVERY_PROPERTIES : dns_query=keycloak-headless.keycloak.svc.cluster.local
JGROUPS_DISCOVERY_PROTOCOL : dns.DNS_PING
KC_CACHE_STACK : kubernetes
KC_PROXY : edge
All reactions