Hi @Niall,
We are invoking camunda message correlation from the helper class as shown below. Just comparing time before and after returning to calculate elapsed time.
It really depends on you’ve configured the wait states in your process and also what exactly your code is doing.
When you’re sending a message to the engine it’s the client thread thats progressing the state not the engine’s threads.
If you have a wait state before your service task it creates a job for the engine to pick up. You could be counting the time in which the job waits to be picked up as well as execution time. in which case change the job executor settings to ensure more jobs get picked up or that the executor has a bigger thread pool might work.
Thanks for your quick reply.
Currently we are using default settings for job-executor
max-jobs-per-acquisition - 3
max-pool-size - 10
queue-capacity - 3
We will try to increase these settings. Pls clarify below.
Do we need to re-create camunda DB to get effect these settings
Do we need to specify these settings in all Camunda-app or which ever app needed.
No need to recreate the database. Just restarting the application should work seamlessly.
If it’s homogeneous cluster setup, then you need to set this property in all the nodes in the cluster. If it’s heterogeneous cluster, then set these properties to the nodes in which job execution is enabled.
opal_deal_eval_processing_user_rule_process.bpmn (8.1 KB)
