Same jobs on separated engines in cluster

[victor1]

Hello everyone!

There are two applications working with the same database.
Applications use the business process involves asynchronous tasks.

There is also an EventListener, which writes processInstanceId for all jobs that have been completed and counts the number of completed jobs. During tests, i saw that one app performs a bit more jobs than another.
For example, if two applications had to perform 1000 jobs as a result of one of them performs about 1050, and another 1000.
When i checked stored processInstanceIds, and saw that there are matching id so both apps execute same jobs.

Please tell me why this might be.
The idea is if AsyncJobExecutor takes the task to work, it must lock it and other JobExecutors that work with same database cant execute it.

[swamy2156]

Any updates on this? Even I too facing similar problem with AsyncJobExecutor in cluster environment.

[trademak]

The async executor will execute jobs created on the same server in the cluster by default. Only when a job takes longer than the default job timeout, it will be executed on another server. Is it possible in your use case that a job execution takes longer than 1 minute?

Best regards,