Hi,
Is there any way by which the claim/complete(Event type) task listener can be executed by the job executor?
The thing is that my task listeners and deployments are in different micro services which connect to the same database. I have used asynchronous before continuations. The job-executor is enabled only in the MS having the listeners. The create type task listener is executed by the job executor but claim and complete task listeners are not executed.
Hi @Shruti ,
Claiming a task will trigger update event and completing a task will trigger complete event. Both events will be always executed in borrowed client thread since it’s an synchronous invocation. It can’t be executed by job executor due to transactional issues and data inconsistency might happen. So an activity(service task types) can be executed asynchronously but not the attached listeners on the user task.
By considering your application setup, it was based on heterogeneous cluster setup, the listeners will be in another node and camunda api implementation/invocation was in another node. This segregation doesn’t make real heterogeneous cluster setup as described by camunda. It should be like the processes, resources, delegation code and listeners should be grouped and deployed in a node for the specific process application. So that each node will have different process applications with its own resources, processes and the delegation code. By saying that, the deploymentAware=true property makes sure that the request should be processed in which node.
Read about the Camunda cluster setup and job execution in heterogeneous clusters.