15.13. Appendix M: Changing the JVM Heap Size

If you encounter errors related to the memory usage of the Java Virtual Machine (JVM), such as java.lang.OutOfMemoryError, it may be necessary to increase the maximum heap size of the JVM.

EKM cluster nodes run JBoss in domain mode. In domain mode, JBoss launches three JVMs, one for each of the following processes: process controller, host controller, and an application server. To change the JVM heap size for EKM, we must change the JVM settings of the application server process. The JVM settings of the application server process are set in the host controller configuration.

To change the JVM heap size, follow these steps:

  1. On each EKM cluster node, stop the EKM cluster node.

  2. Edit the JBoss host controller configuration (see JBoss Domain Mode and Configuration). Find the lines:

    <servers>
       <server name="node1" group="ekm-server-group">      
          ...
          ...
          <jvm name="default">
             <heap size="256m" max-size="4096m" />
             <jvm-options>
                <option value="-XX:MetaspaceSize=128m" />
                <option value="-XX:MaxMetaspaceSize=512m" />
          </jvm>
       </server>
    </servers>
    
  3. Change the value of the max-size parameter (shown above in bold) to the desired value, in megabytes, for the maximum heap size of the JVM.

  4. On each EKM cluster node, start the EKM cluster node.


Note:  It is rarely necessary to change the JVM heap settings of the JBoss process controller and host controller processes. If necessary, these can be changed by editing the corresponding options in the ekm_start control script, and (Windows only) the Java Service Wrapper configuration: wrapper.conf.



Release 18.2 - © ANSYS, Inc. All rights reserved.