Expand my Community achievements bar.

SOLVED

codecache usage 99% /system/console/memoryusage

Avatar

Level 2

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.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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

View solution in original post

3 Replies

Avatar

Employee Advisor

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

Avatar

Level 2

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%.

 

 

\

Avatar

Correct answer by
Employee Advisor

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