CA APM 10.7 EM installer fails to add GC options for new EM install

Document ID : KB000093572
Last Modified Date : 07/05/2018
Show Technical Document Details
Issue:
Using the APM 10.7.0.45 Introscope Enterprise Manager (EM) installer:
1. When installing a NEW Enterprise Manager (NOT AN UPGRADE) the default JVM properties do not include any GC properties i.e. the default JVM properties shown during the install are: 
-Xms1024m -Xmx1024m -Djava.awt.headless=true -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./logs/ -Xss512k

After the install the files Introscope_Enterprise_Manager.lax (all platforms) and EMService.conf (Windows) also show the same e.g.  Introscope_Enterprise_Manager.lax file:
lax.nl.java.option.additional=-Xms1024m -Xmx1024m -Djava.awt.headless=true -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./logs/  -Xss512k

Compared with the 10.5.2.0 EM installer which included GC properties "XX:+UseConcMarkSweepGC -XX:+UseParNewGC"


2. When installing a NEW WebView the default JVM properties do include GC properties "-XX:+UseG1GC -XX:MaxGCPauseMillis=200" e.g. the Introscope_WebView.lax file shows:
lax.nl.java.option.additional=-Xms256m -Xmx1024m -Djava.awt.headless=true -Dorg.owasp.esapi.resources=./config/esapi -Dsun.java2d.noddraw=true -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -Dorg.osgi.framework.bootdelegation=org.apache.xpath 
Environment:
APM 10.7.0.45 Introscope Enterprise Manager Installer (all platforms)
Cause:
The EM installer should be including the same GC properties for the EM install as it does for the WebView install.
Resolution:
Manually add the GC options after the install as follows:
a. Linux/Unix and Windows (when not running EM as Windows service):
Add "-XX:+UseG1GC -XX:MaxGCPauseMillis=200" to the lax.nl.java.option.additional property in the Introscope_Enterprise_Manager.lax file e.g.
lax.nl.java.option.additional=-Xms1024m -Xmx1024m -Djava.awt.headless=true -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./logs/  -Xss512k -XX:+UseG1GC -XX:MaxGCPauseMillis=200

b. Windows when running EM as a Windows service:
Add "-XX:+UseG1GC" and "-XX:MaxGCPauseMillis=200" to the EMService.conf file e.g.
wrapper.java.additional.1=-Djava.awt.headless=false
wrapper.java.additional.2=-Dmail.mime.charset=UTF-8
wrapper.java.additional.3=-Dorg.owasp.esapi.resources=./config/esapi
wrapper.java.additional.4=-XX:+HeapDumpOnOutOfMemoryError
wrapper.java.additional.5=-XX:HeapDumpPath=./logs/
wrapper.java.additional.6=-Xss512k
wrapper.java.additional.7=-XX:+UseG1GC
wrapper.java.additional.8=-XX:MaxGCPauseMillis=200
Additional Information:
1. This problem does not occur for an 10.7 EM upgrade where any existing GC options in the Introscope_Enterprise_Manager.lax & EMService.conf files are retained.
2. With the use of Java 1.8 the G1 Garbage Collector is now being recommended especially for the large heaps that are typically used for MOM & Collectors EMs in an APM cluster.
3. The problem is planned to be fixed in a future 10.7 Service Pack or Hot Fix.