The default configuration of the Symantec Endpoint Protection Manager (SEPM) is designed to minimize the memory and disk-space footprint. However, in larger organizations which may be leveraging multiple groups and/or replicated sites, the default settings may cause the system to under-perform or may generate error messages.
When the current maximum amount of Java Heap space is insufficient, you may experience the following errors or symptoms:
ATTENTION: Server side cache reached high water mark.
INFO: Server side cache reached high water mark.
java.lang.OutOfMemoryError: Java heap space
The SEPM is a Java-based application, and consequently much of its performance will be related to the size of the Java Heap.
Modifying the settings that control the size of the Java Heap will improve the performance of a wide variety of the functions performed by the SEPM.
Increase the the Java Heap space assigned to the SEPM service and consoles.
Note: Please backup the Registry before making the changes mentioned below.
Note : Maximum JVM Option Number 1 value can go up to -Xmx10240m if above values doesn't work & same needs to be added in Sesm.bat as well as successfully tested.
Note: Before modifying the file below, please make a backup copy of the file.
How to modify the max-heap-size value for the downloaded JNLP file:
Note: The additional RAM will be allocated immediately following the service restart. You may see an immediate (but temporary) rise in disk and cpu activity as the page file size is increased. The max size varies depending on OS and the state of the machine.
The Heap Size for Symantec Endpoint Protection Manager is specified with two values, stored in the registry.
The application will automatically increase the size of the Java Heap as required until it encounters the configured maximum size. These values can be increased to better suit the available resources on the computer. Performance can be optimized by following the guidelines below:
The Java Heap minimum size must not be larger that the Java Heap maximum size.
If the working size of the Java Heap exceeds the available physical RAM, the computer will begin paging the Java Heap. This will dramatically increase Disk I/O and reduce the overall performance.
Note: Always allow for at least 256 MB to be allocated to the Operating System. For Example: On a computer with 1 GB of RAM, the maximum value for the Java Heap should not exceed 768 MB.
The value of MinHeapFreeRatio and MaxHeapFreeRatio modify garbage collection characteristics (the ratio of free space to live objects within the heap). The values specified in this document are the defaults for JVM and they provide a good mixture of performance and reliability.
Note: Example of "sesm.bat" in 14.3 RU2 (default installation on 64-bit server with enterprise size settings):
@start "SESM" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre11\bin\javaw.exe" --module-path="C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\jmods" --add-modules=javafx.base,javafx.controls,javafx.graphics,javafx.swing,javafx.web --add-opens java.security.jgss/sun.security.jgss=java.base --add-opens java.security.sasl/com.sun.security.sasl=java.base --add-opens java.xml.crypto/org.jcp.xml.dsig.internal.dom=java.base --add-opens java.smartcardio/sun.security.smartcardio=java.base --add-opens jdk.crypto.mscapi/sun.security.mscapi=java.base -Dprism.order=sw -Xms2048m -Xmx4096m -XX:MinHeapFreeRatio=50 -XX:MaxHeapFreeRatio=100 -XX:NewRatio=15 -Djava.locale.providers=COMPAT -Dcatalina.home="C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat" -Dscm.console.conf="C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties" -Dsun.locale.formatasdefault=true -cp "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\scm-ui.jar;C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre11\lib\*" com.sygate.scm.console.ConsoleMain %*
For other examples of sesm.bat and parameters, see Replication fails with a Java error "GC overhead limit exceeded"