Unable to start Introscope Enterprise Manager and see the error message, "Could Not Create Java Virtual Machine."

Document ID : KB000045641
Last Modified Date : 14/02/2018
Show Technical Document Details

 Problem: 

 Introscope Enterprise Manager fails to start with the following error message reported on the EM Log:

 

 Conflicting collector combinations in option list; please refer to the release notes for the combinations allowed
 Error: Could not create the Java Virtual Machine.
 Error: A fatal exception has occurred. Program will exit.

 

 Environment:  

 APM 10.1.0.16
 Solaris 10
 JVM 1.8 64 bit

 

 Cause: 

  Caused by the switches "UseG1GC"  and "UseParNewGC" enabled same time in Java Options on the IntroscopeEnterpriseManager.lax (Linux and Windows non-service.  If EM on Windows is installed as a service, then edit the EMService.conf file).

 Example:

 lax.nl.java.option.additional=-Xms512m -Xmx1024m -Djava.awt.headless=false
 -XX:MaxPermSize=256m -Dmail.mime.charset=UTF-8 -showversion -XX:+UseConcMarkSweepGC
 -XX:+UseG1GC -XX:+UseParNewGC -XX:CMSInitiatingOccupancyFraction=50 -Xss512k

 

 Resolution:

 1. '-XX:+UseG1GC' cannot be used with '-XX:+UseConcMarkSweepGC' or '-XX:+UseParNewGC' (however the latter two can be used together).  Best practice is to use either G1GC or the other two.  It has been observed that G1GC works well on Java 1.7 and 1.8 with large heaps.  G1GC seems to have an issue with smaller heaps.

 2. Save the IntroscopeEnterpriseManager.lax 

 3. Restart the Enterprise Manager