Boomi · Boomi runtime
OutOfMemoryException
Short answer
An OutOfMemoryException in Boomi means the runtime ran out of memory while processing, usually on large or concurrent data sets. Split or batch the data so it is not held in memory at once, and give the runtime more heap if the machine has it.
VerifiedLast verified
01Error text
OutOfMemoryException02Likely causes
- One large file is processed without batching.
- Many processes run at once.
- Many large data sets are processed at once.
- A memory inefficiency in the runtime.
- The machine is out of physical or virtual memory.
03How to fix it
- Run large loads that use technology connectors at different times.
- For large CSV files, add a Data Process step with Split Documents.
- Use a Flow Control step to process one document at a time.
- For database reads, use the Grouping options. For database writes, use the Commit options.
- Size the heap for the volume. The default is 512 MB of RAM for low to medium loads; the docs suggest 1 GB for 100,000 records, 2 GB for 200,000 to 500,000 and 4 GB or more above that.
- To capture a heap dump for analysis, set Heap Dump on Out of Memory Error on the runtime's Advanced tab.
04Official documentation
→Related errors
- Low memory in memory poolThis container log message means the runtime's heap use went over the Low Memory Mode Threshold, so documents are flushed to disk and disk I/O rises. Increase the JVM heap if the machine has the physical RAM.
- Process discarded due to system load: execution queue maximum size reachedThis message means the node's execution queue was full, so the runtime discarded the submitted process instead of queuing it. Reduce how many executions arrive at once, or review the Maximum Queued Executions per Node and Maximum Simultaneous Executions per Node properties.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Boomi work:Open Boomi jobsBoomi rates and salaries