In ARS 9.x the armonitor.log file shows arserver process crashing and causing heap dump: ........................... <MNTR> <TNAME: Thread-3 > <INFO > <ProcessMonitor$1> <ProcessMonitor.java:198> /* Mon May 02 16 11:08:43.0049 */ java.lang.OutOfMemoryError: Java heap space ........................... |
Please refer to KA 000111538 for Best Practice Java Settings Check the following: 1. Increase maximum heap size Set vm.maximum.heap.size. This needs to be set in arserver.config (Windows only) located in the ‘ARSystem’ directory. For Linux or Solaris, the file name is arserverd.conf. - Medium size environments with 800-2,000 concurrent users and 16 GB RAM, set jvm.minimum.heap.size to at least 8589934592. set jvm.maximum.heap.size to at least 8589934592. - For a Large environment (2000-5000 concurrent users and 32 GB RAM) set jvm.minimum.heap.size to at least 21474836480. set jvm.maximum.heap.size to at least 21474836480. 2. Add additional garbage collection parameters to arserverd.conf. Note option 15 to 18 as example: ...................................... # JVM options (number indicates option order) jvm.option.1=-javaagent:../lib/spring-instrument-4.1.2.RELEASE.jar jvm.option.2=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl jvm.option.3=-Dlogback.configurationFile=file:../conf/logback_server.xml jvm.option.4=-Xss2M jvm.option.5=-XX:MetaspaceSize=384M jvm.option.6=-XX:MaxMetaspaceSize=512M jvm.option.7=-Dcom.sun.management.jmxremote jvm.option.8=-Dcom.bmc.arsys.boot.flavor=server jvm.option.9=-XX:OnOutOfMemoryError=./kill-server jvm.option.10=-Djetty.home=../jetty jvm.option.11=-Dorg.eclipse.equinox.http.jetty.autostart=false jvm.option.12=-XX:ErrorFile=file:../db/arserverjvmcrash_PID%p.log jvm.option.13=-XX:+HeapDumpOnOutOfMemoryError jvm.option.14=-XX:HeapDumpPath=../Logs jvm.option.15=-XX:+UseConcMarkSweepGC jvm.option.16=-XX:+UseParNewGC jvm.option.17=-XX:+UseCompressedOops jvm.option.18=-XX:NewRatio=2 jvm.option.19=-XX:+DisableExplicitGC
|