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:
-Xmx512mto the Runtime parameters for the JVM for the
-Xmx512mto the end of the existing values on its own line.
/etc/sysconfig/jitterbitin a text editor.
Find this line in that file, and edit the options:
export JAVA_OPTS="-Xms512m -Xmx1024m"
Restart the Jitterbit tomcat service:
$ /etc/init.d/jitterbit stop_tomcat $ /etc/init.d/jitterbit start_tomcat
Restart all the Jitterbit services:
$ /etc/init.d/jitterbit restart