topic Re: Failed timers and due timers causing login and restart problems in Alfresco Archive

Failed timers and due timers causing login and restart problems

jflukkien — Thu, 11 Aug 2016 08:24:11 GMT

Hi all, The last 3 days i've been working on an issue we've encountered when using activiti and i'm wondering how to improve our setup to be more resilient to this issue popping up again.Last saturday we had 30 processes failing because of a mismatch in what our activiti instance was expecting in da

Re: Failed timers and due timers causing login and restart problems

warper — Thu, 11 Aug 2016 15:53:52 GMT

What engine properties do you use?
How long does it take to complete(fail) one synchronous part of a job?
It's possible to get into trouble if you use several engines, your job takes too long and job lock is released before commit of initial job execution.

Re: Failed timers and due timers causing login and restart problems

jflukkien — Fri, 12 Aug 2016 07:26:04 GMT

We have the following Process Engine Config:

JobExecutorActivate is true
EnableDatabaseEventLogging is true
DatabaseSchemaUpdate is true

And one of the workflows that ran this morning took a total of 86 ms from start to finish where the longest synchronous part of a job takes 50 ms (but that is an http call so that is not that strange).

Re: Failed timers and due timers causing login and restart problems

warper — Fri, 12 Aug 2016 15:33:15 GMT

Such a speed is beyond my understanding, to be honest. My local activity instance running one process test on mocks does something like 1.5 script tasks per second.
How do you set up retry counts/times for failed processes? Something you describe can happen if you have nearly zero retry timer and a lot of retries, so failed job gets executed over and over for each of 30 failing processes. Otherwise activiti should try them once and sleep happily for the duration of retry interval.