If your process crashes with "Java heap space" error, your Runtime experiences a lack of memory :
com.indy.engine.common.exceptions.EngineExceptionI: Unknown java.lang.error working with the engine, contact your supplier
at com.indy.engine.action.common.ActionCodeTypeI.executeCode(SourceFile:1275)
at com.indy.engine.action.common.ActionCodeTypeI.run(SourceFile:1323)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.OutOfMemoryError: Java heap space
at oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:819)
at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:972)
at oracle.jdbc.driver.T4CStatement.execute_maybe_describe(T4CStatement.java:463)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1051)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1184)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at com.indy.engine.actionCodes.SqlFileExportActionCodeI.executeSimpleCode(SourceFile:807)
at com.indy.engine.action.common.ActionCodeTypeI.executeCode(SourceFile:1249)
... 2 more
You can try to increase the STAMBIA_MAX_MEMORY in initvariables script :
set STAMBIA_INIT_MEMORY=32m
set STAMBIA_MAX_MEMORY=512m
set STAMBIA_STACK_SIZE=256k
But sometimes, that won't be enough. You'll have to check the operations done in your process. Seek for the SQL operations and maybe reduce the fetch batch size parameter. It can also happens if you handle a huge XML file. In that case, you probably need to increase the STAMBIA_STACK_SIZE parameter.
