• Prevents Out Of Memory Errors


The recommendation below is assuming there is at least 8GB RAM on the Server and half of the provisioned memory is being allocated to Tomcat. Adjust Memory accordingly



Configuring Tomcat (Application)

  1. Edit Ephesoft_Installation_Folder\JavaAppServer\bin\startup.bat using a text editor.
  2. Please find JAVA_OPTS in startup.bat and copy the settings against JAVA_OPTS to a new instance of text editor. (in case we want to revert to earlier settings.)
  3. Now edit JAVA_OPTS by appending below mentioned settings to its end.

-Xms4096m –Xmx4096m –Xss512k -XX:MaxPermSize=1024m -XX:PermSize=1024m

  1. Please make sure that we don’t have duplicate entries for above mentioned optioned in JAVA_OPTS.
  2. Save startup.bat


Configuring Tomcat (Windows Service)

  1. Open tomcat service configuration by right clicking on the Ephesoft_Installation_Folder\JavaAppServer\bin\EphesoftEnterprise.exe file.
  2. Right Click and Select ‘Run as administrator’
  3. Go to Java tab.
  4. Now append following configuration under Java Options:



Please make sure none of above entries are duplicated in Java Options

Edit Initial memory pool option to value 4096.

Edit Maximum memory pool option to value 4096.

Thread Stack Size to 512

Apply these settings and start the server.





In Linux you need to edit the settings located in the /opt/Ephesoft/JavaAppServer/bin/

export JAVA_OPTS=‘-Djava.library.path=$EPHESOFT_NATIVE$APP_SERVER_TEMP -Ddcma.home=$DCMA_HOME -Xmx4096m -Xms4096m -XX:PermSize=1024m -XX:MaxPermSize=1024m -Duser.language=en -XX:-UseSplitVerifier -Djava.awt.headless=true’


By using these recommended minimum settings you will help prevent Out of Memory Errors (OOME). Please note that these are minimum specs for you memory configuration for Tomcat and should be used as a starting point. If you continue to receive OOME issues you may need to continue adjusting the Heap or Memory size in the Tomcat configurations or troubleshoot the reason why you are exceeding the memory for the application. (Tip: for troubleshooting Thread or memory issues use tools like jvisualVM)