nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

jobExecutor threads

richard1

I have another newbie question. If I have a timer that is set to go off at a certain time and I have 100 instances of a workflow, how many threads would be started to handle those jobs? Would it be 100? If so is there a way to throttle it so only 10 threads could be running at any 1 time? This means my job may not get started exactly when I wanted but it also means I do not have too many things running at the same time.

Thanks,
Richard

Find more posts tagged with

Comments

jbarrez

There is a default size of the threadpool for job executors.
I also believe there is an undocumented setting for changing that size, but I can't directly find it.
But it's already asked on the forum in the past, so maybe the seach can help there.

ronald_van_kuij

I do not think it is configurable from what I remember

richard1

Open Source is awesome. Looking into the code, the max number of threads in the pool is 10 by default. So by default it is doing what I wanted.

I do think I could set the number of threads in my Spring configuration by creating a JobExecutor bean, set maxPoolSize on it. Then set the JobExecutor on the SpringProcessEngineConfiguration and then it could be anything I wanted it to be.

Thanks,
Richard