# Flowable 7.2.0: Node Affinity Hoards All Jobs – All Async Jobs Locked by Node 1 while only 8 are being processed

**URL:** <https://forum.flowable.org/t/flowable-7-2-0-node-affinity-hoards-all-jobs-all-async-jobs-locked-by-node-1-while-only-8-are-being-processed/12547>\
**Category:** Flowable Engine\
**Created:** [February 27, 2026, 3:34pm UTC](https://forum.flowable.org/t/flowable-7-2-0-node-affinity-hoards-all-jobs-all-async-jobs-locked-by-node-1-while-only-8-are-being-processed/12547 "2026-02-27T15:34:21Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ROY](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@ROY](https://forum.flowable.org/u/ROY)\
**Post date:** [March 10, 2026, 8:47am UTC](https://forum.flowable.org/t/flowable-7-2-0-node-affinity-hoards-all-jobs-all-async-jobs-locked-by-node-1-while-only-8-are-being-processed/12547/10 "2026-03-10T08:47:54Z")

</div>

HI @filiphr@joram

That was it! Using the `spring.task.execution.pool.*` properties instead of the `flowable.process.async.executor.*` properties fixed the issue immediately.

Because the default Spring `queue-capacity` was `Integer.MAX_VALUE`, Node 1 was indeed hoarding every job. Once I limited the Spring queue capacity, the `unacquireJobAfterRejection` logic triggered perfectly, and Node 2 started picking up the excess load.

As a followup topic, it would be better to update documents like [Advanced · Flowable Open Source Documentation](https://www.flowable.com/open-source/docs/bpmn/ch18-Advanced) about how spring parameters are used.

Thank you again for helping me to understand this better.

Regards,  
Roy

---

_[View the full topic](https://forum.flowable.org/t/flowable-7-2-0-node-affinity-hoards-all-jobs-all-async-jobs-locked-by-node-1-while-only-8-are-being-processed/12547)._