Skip to Content

Increase the Jitterbit Tomcat heap size on Jitterbit private agents

The parts of Jitterbit that are implemented in Java (currently LDAP and JDBC) run in Apache Tomcat which requires a Java Virtual Machine. The default maximum heap size of the JVM may not be enough for you in which case you will get an error, possibly something such as:

Java heap space Cause stack trace: java.lang.OutOfMemoryError: Java heap space

Note: You can get this error on the client, but this FAQ only refers to the private agent maximum heap size.

Increasing the maximum heap space can also boost performance if you are reading or writing large JDBC data sets, since it decreases the need for garbage collection in the JVM.

If you want to increase the maximum heap size, you do so by editing the JVM settings. If there already is a value, then adjust as appropriate, as described here for each operating system:

  • Windows

    • To set it globally for all Java applications:

      1. Open the Java Control Panel (Start -> Control Panel -> Java).

      2. Select the Java tab.

      3. View the Java Runtime Environment Settings.

      4. Add -Xmx2048m (or higher) to the Runtime parameters for the JVM for the x86 architecture.

      5. Restart the Jitterbit Tomcat Server service.

    • To set it only for the Jitterbit Tomcat instance:

      1. Start the Registry Editor: In the Windows toolbar search box, enter "Run", press enter, and in the resulting dialog, enter regedit.

      2. Allow the Registry Editor to open and make changes to your device.

      3. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\Jitterbit Tomcat Server\Parameters\Java

      4. Double-click on Options and add -Xmx2048m (or higher) to the end of the existing values on its own line.

      5. Restart the Jitterbit Tomcat Server service.

  • Linux

    1. Open the file /etc/sysconfig/jitterbit in a text editor.

    2. Find this line in that file, and edit the options:

      export JAVA_OPTS="-Xms512m -Xmx2048m"

    3. Either:

      • Restart the Jitterbit Tomcat service:

        $ /etc/init.d/jitterbit stop_tomcat
$ /etc/init.d/jitterbit start_tomcat

        or

      • Restart all the Jitterbit services:

        $ /etc/init.d/jitterbit restart