Changing the Maximum Memory of Tomcat Service

image_pdfimage_print

Integrator processes, which are run by a Tomcat service, can consume a great deal of heap memory. The default amount of memory the Java Virtual Machine (JVM) is allowed to allocate is 1024 MB, which may not be enough, especially for 64-bit systems. To improve performance, you can change the maximum amount of heap memory available.

The process of changing the allocated memory is different for Windows and Linux systems, as Jedox uses two separate Tomcat services on Linux. Please refer to the appropriate instructions below.

For details on changing memory allocation for R integration, see RScript Transform.

On Windows:

  1. Change the value of Max_Memory in the file …\tomcat\bin\setenv.bat.
  2. Execute …\tomcat\bin\serviceRemove.bat. This stops and removes the service.
  3. Execute …\tomcat\bin\serviceInstall.bat. This installs and starts the service.

On Linux:

As of Jedox 2019.2, Tomcat runs a separate Tomcat service for Integrator (tomcat-etl), which means that you can allocate more memory directly to Integrator processes. You can also change the heap memory allocation for other Jedox processes using the service tomcat-rpc. Each service has its own setenv.sh file where the maximum memory allocation can be changed, and each service must be started and stopped separately.

  1. Stop the relevant Tomcat service via ./jedox-suite.sh stop tomcat-etl OR ./jedox-suite.sh stop tomcat-rpc
  2. Change the value of Max_Memory in the file …/tomcat-etl/bin/setenv.sh OR  …/tomcat-rpc/bin/setenv.sh
  3. Restart the Tomcat Service via ./jedox-suite.sh stop tomcat-etl OR ./jedox-suite.sh stop tomcat-rpc
image_pdfimage_print