High Availability Behavior

[nvulchev1]

Hi,
I am testing activiti in high availability scenario (two activiti web apps with activiti engines and only one DB).
During the tests I observe that if one of the engines takes a task for execution the task (job) is locked in the DB. Then I kill the engine OS process that locked the job. I observe that the job is actually marked as unprocessed and unlocked only after 5 minutes (the default value of lockTimeInMillis as I see in other topics). Only then another engine could take take the job for processing.

So my question is whether there is any other mechanism by which the available activiti engines could 'see' that the acquired and locked in the DB job is not anymore processed by a dead engine.

Thanks!

[jbarrez]

No, that's currently the way it works. If you want to have like a heartbeat that updates that column when the heartbeat dies, that would be custom code.