Boomi · Boomi runtime
Low memory in memory pool
Short answer
This 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.
VerifiedLast verified
01Error text
[com.boomi.container.config.ResourceManager handleMemoryNotification] Low memory in memory pool02Likely causes
- Heap use exceeded the Low Memory Mode Threshold (
com.boomi.container.resource.lowMemoryThreshold). The threshold is 90% at 4 GB or more of heap and 60% at 512 MB or less, interpolated in between.
03How to fix it
- Increase the JVM heap if physical RAM allows.
- To investigate what is using the heap, set the runtime property Generate Heap Dump on Low Memory and run again. The log entry "Start generating heap dump on low memory status in file" gives the file location.
- Reduce the memory the process needs at once, for example by splitting documents or lowering parallelism.
04Official documentation
→Related errors
- OutOfMemoryExceptionAn 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.
- 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