Keycloak uses Infinispan (an in-memory caching solution), which consumes
most of the heap for the JVM.
The "GC overhead limit exceeded" tells you that the JVM was fighting for
its live trying to release as much memory from the heap as it could and
didn't succeed in a certain amount of time.
The easiest solution is to increase your heap. Or a more complicated one -
tune the eviction parameter on your caches.
On Mon, Nov 5, 2018 at 3:23 PM Lahari Guntha <lahari.guntha(a)tcs.com> wrote:
?Hi all,
We are Using Keycloak to have SSO enabled for different applications. It
was working fine. All of a sudden we were unable to access keycloak.
After checking logs we came to know that "GC overhead limit exceeded".
May I know how to resolve this Issue?
Thanks and Regards,
Lahari G
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user