Job executor not picking up job

[akkujain93]

@ryans58

he Job Executor picks up a job, it locks it to avoid having any other Job Executor threads pick up that same job. If the job runs to completion, it is then removed from the ACT_RU_JOB table. If it fails, an exception message will appear. Thus, i

This was happening because I am having a heterogeneous cluster, which is having configuration as deployment aware.
So If I restart the node, all the in memory data has been gone.
So jobExecutor never fetch the job because of deployment_id persisted during the async call doesn’t match to the in memory data.
It is working fine in homogenous cluster setup or in case of deployment aware false.
For heterogeneous setup, I have to register all the deployments again while server startup.
For that I raised a question -

Duplicate Process Definition

I am adding 1 more question here. I am having Heterogeneous Cluster setup. Now I deployed some process applications through modeler. So the process engine will maintain in memory about new deployments. But If I am restarting my node. I will not able to identify which all deployments have been pushed through this node as this information doesn’t persist anywhere. If I am trying to do something like repositoryService.createProcessDefinitionQuery().list(); It will give me whole processDefiniti…