REV_ count is 900 and RETRIES_ count is 3 - How could this possible in ACT_RU_JOB

[rakesh1]

Hi Everyone,

We are seeing weird behavior of ACT_RUN_JOB table in 5.10. We are aware that default retry count for a Activiti job is 3. However in our project a job was called more than 900 times (everytime it is rollingback with our internal code issue).  For this particular job RETRIES_ count is still showing as 2 - not sure whats happening background.

Can someone please explain us what could be the possibility for this kind of issue. We want to make changes to retry a job only for 3 times in case of rollbacks.

[rakesh1]

I want to add one more point here..

In Activiti 5.10 version we do not have jvm column in ACT_RUN_JOB table. However we tweaked Activiti engine source code to accommodate this column. So there is no possibility of rollbacks of a particular job in clustered environment because of optimistic locking.

[jbarrez]

I'm not following here. What is the 'jvm' column? If a job fails (exception propagates to the parent caller) there is a transaction rollback listener that sets the retries count with -1. That should work and is tested in our QA.