Boomi · Boomi runtime
Process discarded due to system load: execution queue maximum size reached
This 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.
VerifiedLast verified
01Error text
Submitted process <execution ID> discarded due to system load: execution queue maximum size reached - queue size: <maxQueuedExecutions>
ContainerOverloadedException: Submitted process <execution id>: execution queue reached the maximum size - queue size <maxQueuedExecutions>. Process discarded due to system load.02Likely causes
- The number of queued executions reached Maximum Queued Executions per Node (
com.boomi.container.maxQueuedExecutions). - Executions queue when the node is already running Maximum Simultaneous Executions per Node (
com.boomi.container.maxRunningExecutions).
03How to fix it
- Runtime properties are set in Manage > Runtime Management: select the runtime, open Properties and go to the Advanced tab.
- Review Maximum Simultaneous Executions per Node and Maximum Queued Executions per Node against the load the node receives and the resources it has.
- Spread schedules or reduce the rate of incoming requests so fewer executions start at the same moment.
- Rerun the discarded execution.
iNotes
The docs describe the property and the message it produces. They do not give a step-by-step fix, so the steps above apply the documented property. Queued executions also time out after Timeout for Queued Executions per Node, which defaults to 59 seconds.
04Official documentation
→Related errors
- SecurityException: Exceeded thread limitThis exception means a forked execution or an execution worker tried to use more threads than the runtime allows. Lower the parallelism in the process, or review the Maximum Execution Threads property.
- Process exceeded maximum execution time limitThese log lines mean the runtime cancelled the execution because it ran longer than the Maximum Forked Execution Time in Cloud. Make the process finish sooner, for example by splitting the work, or review that property.
- 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.
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