Keycloak runs into OOM when starting
See original GitHub issueDescribe the bug
Enabling the “standard auth service”, Keycloak comes up and directly runs into an out-of-memory situation.
To Reproduce Steps to reproduce the behavior:
- Deploy EnMasse with
-a standard
- Look at the logs of the keycloak pod
Expected behavior
Not run into OOM situation.
Logs
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
[keycloak-user] OOM at startup with 1 million sessions
I start one Keycloak node configured with a remote-cache and Xmx=4G >> >> Note that I use a remote-store in KC as it...
Read more >Is Keycloak experiencing memory leak? - Stack Overflow
I started investigating in a docker environment where i only run keycloak and postgres and leave everything idle.
Read more >Keycloak dies every few days for high memory usage
I have a Keycloak in a VPS running as SSO for the rest of the architecture. But every few days, without apparently any...
Read more >Untitled
JBossThread.run(JBossThread.java:320) Caused by: java.lang.RuntimeException: Failed to construct public org.keycloak.services.resources.
Read more >[keycloak-user] Uncaught server error: java.lang ...
I am ok if there are few failures and few success and the system runs in > this manner so that ... If...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that I had the same situation as before, but this time the keycloak instance did not restart.
I would say this looks good!
@ctron This should be fixed on 0.25.0. Would you be able to try it and see if it resolves the issue?