Memory leak | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
kautuk_sahni
kautuk_sahniAccepted solution
Employee
Sep 18, 2017 3:42 AM UTC

Adding some more information here:

"CacheManager: resizeAll" entries in Log: When functionality is developed for AEM WCM, JCR Sessions may be opened (comparable to opening a database connection). If the opened sessions are never closed, your system may experience following symptoms:

• The system gets slower and slower Miscellaneous

• You have a lot of "CacheManager: resizeAll" entries in the log file (the number behind size=... is the number of caches; each session opens a few caches)

• From time to time the system runs out of memory (after a few hours, days, or weeks - depending on the severity)

Read this:- Troubleshooting Scenarios

Must Read:- Analyze Unclosed Sessions

Helpx on Memory problem:- Analyze Memory Problems

~kautuk

Kautuk Sahni

2 replies

kautuk_sahni
kautuk_sahniAccepted solution
Employee
Sep 18, 2017 3:42 AM UTC

Adding some more information here:

"CacheManager: resizeAll" entries in Log: When functionality is developed for AEM WCM, JCR Sessions may be opened (comparable to opening a database connection). If the opened sessions are never closed, your system may experience following symptoms:

• The system gets slower and slower Miscellaneous

• You have a lot of "CacheManager: resizeAll" entries in the log file (the number behind size=... is the number of caches; each session opens a few caches)

• From time to time the system runs out of memory (after a few hours, days, or weeks - depending on the severity)

Read this:- Troubleshooting Scenarios

Must Read:- Analyze Unclosed Sessions

Helpx on Memory problem:- Analyze Memory Problems

~kautuk

Translate
Kautuk Sahni
joerghoh
Employee
Sep 17, 2017 8:52 PM UTC

Can you provide some of these messages?

And an out-of-memory can have many causes: Heap size to low for the workload (especially important when you do heavy asset ingestion) or memory leaks. You should analyze the gc logs and check if the heap usages spikes or slowly increases to a point where the instance runs into OOM.

Jörg

Translate