Repository navigation
|
cross posting from https://keycloak.discourse.group/t/memory-grows-until-heap-exhausted-huge-defaultsegmenteddatacontainer/29548 Curious if anyone's seen this? Keycloak I found a similar issue in https://access.redhat.com/solutions/7011043 but alas, I don't have access to a RH subscription to see the "solution". |
Replies: 2 comments 5 replies
|
If you are not using persistent sessions the caches will default to unlimited sizes. What kind of workload are you running? If you are simply running a scenario where sessions are created and left to implicitly clean up you may be accumulating much more memory footprint than you would expect as sessions have a long TTL and idle time by default. |
|
I looked at the infinispan metrics and noticed that it was accumulation of 350K+ They had the Login timeout value set to 30 days, so it was just keeping everything in memory: (as a side note, I'm curious why they recommend the value to be "relatively long, such as 30 minutes or more" given that long login timeouts create a potential vulnerability to session fixation attacks) Sorry I didn't think to look there. Problem solved! |
-
Reference
I looked at the infinispan metrics and noticed that it was accumulation of 350K+
authenticationSessions:They had the Login timeout value set to 30 days, so it was just keeping everything in memory:
(as a side note, I'm curious why they recommend the value to be "relatively long, such as 30 minutes or more" given that long login timeouts create a potential vulnerability to session fixation attacks)
Sorry I didn't think to look there. Problem solved!