codecache usage 99% /system/console/memoryusage | Community
Skip to main content
Level 2
October 16, 2015
Solved

codecache usage 99% /system/console/memoryusage

  • October 16, 2015
  • 3 replies
  • 1613 views

Code Cache usage is at 99% at /system/console/memoryusage in my cq instance.

I am trying to increase the ReservedCodeCacheSize further. Please let me know if this will fix the issue.

Please let me know if this will fix this issue.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

You can increase the codecache with this statement (assuming an Oracle JVM);

-XX:ReservedCodeCacheSize=128M

which sets it to 128 Megabyte.

If this changed setting doesn't show up in your felix console (so it does not have an effect), you might add the commandline parameter "-nofork" to the start command, which prevents the launchpad to spawn a new JVM.

Jörg

3 replies

joerghoh
Adobe Employee
Adobe Employee
October 16, 2015

Hi,

can you tell me, why this metric is important to you? I never had to care about it in my AEM projects.

Jörg

tekyAuthor
Level 2
October 16, 2015

Hi Jörg,

The reason is because we are seeing the following error in logs:

 The activate method has thrown an exception (java.lang.VirtualMachineError: out of space in CodeCache for adapters) java.lang.VirtualMachineError: out of space in CodeCache for adapters

Also as you can see in memorymanagement console the codecache usage is 99%.

 

 

\

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

You can increase the codecache with this statement (assuming an Oracle JVM);

-XX:ReservedCodeCacheSize=128M

which sets it to 128 Megabyte.

If this changed setting doesn't show up in your felix console (so it does not have an effect), you might add the commandline parameter "-nofork" to the start command, which prevents the launchpad to spawn a new JVM.

Jörg