Troubleshooting
Problem
While Building entities Jar by running the ./deployer.sh -t entityDeployer causing OOM.
Symptom
System get hung or throws Out of Memory error in the console. You can see bellow stack trace in console or log.
build:
[javac] /apps/Sterling92/properties/entityDeployer.xml:694: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] /apps/Sterling92/properties/entityDeployer.xml:707: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 3502 source files to /apps/Sterling92/repository/entitybuild/classes
[javac]
[javac]
[javac] The system is out of resources.
[javac] Consult the following stack trace for details.
[javac] java.lang.OutOfMemoryError: GC overhead limit exceeded
Cause
As deployer rebuilds the jar, it takes more memory to recompile and rebuild the jars.
Diagnosing The Problem
Check the log on which entity target system is throwing Out of Memory. Go to entityDeployer.xml file which is in <INSTAL_DIR>\properties folder and browse to the target where OOM is. Look in to the memory arguments and check the value associated with it.
Resolving The Problem
Check the entityDeployer file and check the memory argument which it is picking and check the corresponding value in sandbox.cfg. Change the value to as needed depend on the Java and total memory.
In the above case, increasing memory parameters in "ADDITIONAL_ANT_COMPILER_TASK_ARGS" helped resolve the out of memory error.
Was this topic helpful?
Document Information
Modified date:
10 May 2022
UID
swg21624058