Deadlocks on multiserver configuration

[sushantmahajan]

Hi,

We are currently facing a few deadlocks and some other exceptions when working in a highly concurrent environment.While analyzing the activiti code version. 5.16 I came across a few things which i didn't quite understand-

1)In ExecuteJobsRunnable, JobExecutorContext is created for every thread, is it really required can we keep this code out of run ().

2) ExecuteJobsRunnable, Context object is modified again and again and JobexecutorContext is being set in run method, can we ckeck if same code can as well be kept out of run().
3) How are transactions managed in activiti(I did not see any @transactions annotation).


Thanks

[trademak]

Hi Sushant,

Is there a specific reason for not using a newer Activiti Engine version? We did improve job handling quite a bit in the latest releases. The first two questions I don't understand, maybe you can provide a bit more details for these. About the third question, we handle transactions on a database level with MyBatis. Every job is handled in a separate transaction and the transaction is committed when the engine has encountered a wait state in the process instance or the process instance has ended.

Best regards,