memory exceptions in the epa.log


Article ID: 197132


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management


We see memory exceptions in the epa.log during the restart of epagent. 

Exception in thread "Thread-15" java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(
        at java.lang.AbstractStringBuilder.ensureCapacityInternal(
        at java.lang.AbstractStringBuilder.append(
        at java.lang.StringBuilder.append(
        at com.wily.introscope.epagent.NetworkServer$
        at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$

Are these log entries about OutOfMemoryError anything we should be concerned about? 


Application Performance Management 10.7


With EPAgent there are two components that are using the memory in this environment.

1- EPAgent
2- APM gateway api plugin/scripts that gets installed with EPAgent.

The default EPAgent heap size is set to the following values.
-Xms16m -Xmx256m

The other memory seems to be used by the APM gateway api plugin/scripts.

This is the reason when we stop EPAgent, we see more free memory available then the max heap size of EPAgent.

This is our suggests to address this memory issue in this environment.

1- increase the physical memory on the machine as we see the free memory is low (less then 1 GB) when EPAgent is running.
2- increase the heap size of EPAgent in the startup script of EPAgent to following.
Example: -Xms512m -Xmx512m

We need these two items to be increased because we see that EPAgent is encountering OutOfMemoryError Java heap space Exception.