# How to disable flowable-\*-jobs threads

**URL:** <https://forum.flowable.org/t/how-to-disable-flowable-jobs-threads/5779>\
**Category:** Flowable Engine\
**Created:** [April 6, 2020, 9:36am UTC](https://forum.flowable.org/t/how-to-disable-flowable-jobs-threads/5779 "2020-04-06T09:36:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jit](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@jit](https://forum.flowable.org/u/jit)\
**Post date:** [April 6, 2020, 9:36am UTC](https://forum.flowable.org/t/how-to-disable-flowable-jobs-threads/5779/1 "2020-04-06T09:36:03Z")

</div>

Hi,

I have a clustered environment consisting of 2 nodes and single DB. Node A is just capable of starting processes and Node B can both start and execute the processes.

But although I set async-executor-activate flag as false at Node A, I can see  
“flowable-reset-expired-jobs”,  
“flowable-acquire-timer-jobs”,  
“flowable-acquire-async-jobs”,  
“flowable-reset-expired-jobs”,  
“flowable-acquire-timer-jobs”,  
“flowable-acquire-async-jobs”,

threads in Node A’s thread dump. When I set this flag to false I was actually waiting nothing related to engine threads in thread dump. Do theese threads reside for a purpose or always being there in TIMED\_WAITING state. I didn’t go deep into source code but is there a chance to disable these threads from starting on startup.

Thanks.

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [April 13, 2020, 11:39am UTC](https://forum.flowable.org/t/how-to-disable-flowable-jobs-threads/5779/2 "2020-04-13T11:39:50Z")

</div>

If you set the activate flag to false, it should not start any of these threads:

[https://github.com/flowable/flowable-engine/blob/master/modules/flowable-job-service/src/main/java/org/flowable/job/service/impl/asyncexecutor/DefaultAsyncJobExecutor.java#L149](https://github.com/flowable/flowable-engine/blob/master/modules/flowable-job-service/src/main/java/org/flowable/job/service/impl/asyncexecutor/DefaultAsyncJobExecutor.java#L149) is called only when the whole executor is started: [https://github.com/flowable/flowable-engine/blob/master/modules/flowable-job-service/src/main/java/org/flowable/job/service/impl/asyncexecutor/AbstractAsyncExecutor.java#L120](https://github.com/flowable/flowable-engine/blob/master/modules/flowable-job-service/src/main/java/org/flowable/job/service/impl/asyncexecutor/AbstractAsyncExecutor.java#L120)

Can you perhaps debug these methods and see what is going on there, and why it does get triggered?