Boomi · Boomi runtime
SecurityException: Exceeded thread limit
Short answer
This 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.
VerifiedLast verified
01Error text
SecurityException: Exceeded thread limit of <maxUserThreads value>02Likely causes
- The execution reached Maximum Execution Threads per Forked Execution (
com.boomi.container.forker.maxUserThreads) or the per Execution Worker equivalent (com.boomi.container.worker.maxUserThreads).
03How to fix it
- Reduce the number of threads the process uses, for example the thread count on Flow Control steps.
- Runtime properties are set in Manage > Runtime Management: select the runtime, open Properties and go to the Advanced tab. Review the Maximum Execution Threads property for forked executions or execution workers.
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.
04Official documentation
→Related errors
- 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.
- IllegalStateException: exceeded active batch limitThis exception means a listener has more active batches than Maximum Number of Active Batches per Listener allows. Let batches complete before new ones start, or review that property.
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