Skip to content

Tech note - OutOfMemory events in version 1.69

An issue has been detected with version 1.69 of Matillion ETL where an instance will become unresponsive if an OutOfMemory event occurs, preventing users from logging in.

To resolve this issue, Tomcat must be restarted manually. Unfortunately, after the restart, Matillion ETL version 1.69 won't automatically notify users that an OutOfMemory event occurred (normally this would appear in the Notices tab).

Below is the workaround to add our OutOfMemory script (oom.sh) back in to the JAVAOPTS settings. Once you have completed these steps, Tomcat should restart automatically if an out of memory (OOM) event occurs up to six times, and a notice will appear in the Notices tab upon restart.

Releases before and after 1.69 are unaffected.

Workaround

  1. SSH into your Matillion ETL instance.
  2. Open the file /etc/sysconfig/tomcat.

  3. Locate the following line:

        JAVA_OPTS='-Djavax.net.ssl.trustStore=/etc/pki/ca-trust/extracted/java/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Djava.security.egd=file:/dev/./urandom -Duser.timezone="UTC"

  4. To the end of the above line, add the following:

        -XX:+UseG1GC -XX:OnOutOfMemoryError=/usr/share/emerald/WEB-INF/classes/scripts/oom.sh'

  5. Thus the entire line should read as follows:

        JAVA_OPTS='-Djavax.net.ssl.trustStore=/etc/pki/ca-trust/extracted/java/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Djava.security.egd=file:/dev/./urandom -Duser.timezone="UTC" -XX:+UseG1GC -XX:OnOutOfMemoryError=/usr/share/emerald/WEB-INF/classes/scripts/oom.sh'

  6. Restart Tomcat: sudo service tomcat restart.

Your Matillion ETL instance should be working as expected.