Hello Chandan, We had a similar case on a big custom project.
We solve it with dedicate a different pool on different server and add a job priority.
When a service will schedule, the service definition indicate which pool would be manage it and the priority help on this pool the let urgent treatment to go fast.
Like this we define two or three pools, small and fast service, long treatment and reporting large user action.
The code to send a job on dedicate pool isn't public at this time, and I think we can do better with some time to improve the service component with a service orchestrator.
Nicolas On 30/05/2025 12:00, Chandan Khandelwal wrote:
Hello All, During recent work with OFBiz involving a large number of background jobs, I observed a limitation in the current setup: OFBiz supports only a single global <thread-pool> configuration in serviceengine.xml. This makes it challenging to manage and optimize the execution of jobs that have different resource requirements and priorities. In high-load scenarios, this can result in lower-priority tasks affecting the performance of more critical jobs. I’m currently exploring this area and would like to understand if others in the community have faced similar challenges. Any thoughts, experiences, or suggestions would be helpful. Looking forward to your input. Kind Regards, Chandan Khandelwal
