/
Workbench throws 'OutOfMemoryError'

Workbench throws 'OutOfMemoryError'

Problem

If the Workbench server is constrained for resources, there is a possibility that Workbench will show errors in workbench log file mci.log soon after startup.

Solution

The JAVA_OPTS environment variable can be set to modify the resource usage of Java. More specifically, you can halve the Java Stack Size from 2MB to 1MB.

e.g. $JAVA_OPTS=-Xss1024K

Related articles



Related content

Workbench memory errors on AIX
Workbench memory errors on AIX
More like this
MettleCI CLI throws error 'java.lang.OutOfMemoryError: Java heap space'
MettleCI CLI throws error 'java.lang.OutOfMemoryError: Java heap space'
More like this
The Workbench is unreachable, or the Workbench service won't start
The Workbench is unreachable, or the Workbench service won't start
More like this
Unit Test fails due to exceeded memory threshold
Unit Test fails due to exceeded memory threshold
More like this
Enabling extended logging for MettleCI Workbench
Enabling extended logging for MettleCI Workbench
More like this
Unexpected DataStage error occurred - Unhandled exception Type=Segmentation error
Unexpected DataStage error occurred - Unhandled exception Type=Segmentation error
More like this

© 2015-2024 Data Migrators Pty Ltd.