Geek Answers Handbook

AEM session object not garbage collected

Over the past month, I have been working on the AEM 6.0 production site, which requires a restart of the instance after a week or so. In this particular case, it is my publisher who fails. Therefore, I studied it even more and found that everything worked fine at first, and after a few days the garbage collection went crazy, so the CPU load increases like crazy. From there I restarted my publisher and waited for the heap heap to come out, when the GC would become irrelevant again and analyze it using the MAT (Memory Analyzer Tool from eclipse). After my inspection, I found that 94% of the heap is occupied by ConcurrentHashMap. I hit this object and found that sessions are a problem or at least one of the main problems. The session timeout value is 0, so there is no timeout on the sessions. My error logs show this type of message:

*WARN* [ip [1432319636774] GET something HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 2 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.

Can I configure session manager in AEM? Has anyone seen this in AEM before? Should I set the session timeout to 1 or some value in particular? Any suggestions would be happy to know how I should proceed to solve this problem?

thanks

+5
source share
1 answer

This is a known problem with oak, which was mainly fixed with Oak 1.0.12. Consider installing AEM 6.0 Service Pack 2 with the latest fixes on top of it, if possible. You should also plan some migration time if you have lib overlays, but the upgrade effort is minimal compared to the daily software issues. You can find the latest AEM fixes here or in the share package .

If you cannot install Service Pack 2, then consider installing all available Oak fixes. There are also some new oak packages: the index you need to install.

+1
source

More articles:


All Articles