topic Re: Weird Activiti Timer Boundary Event Behavior in Alfresco Archive

Weird Activiti Timer Boundary Event Behavior

tradus_yogesh — Sat, 29 Jun 2013 12:09:23 GMT

Hi,I am facing an issue pertaining to Timer Boundary Events. These timers are attached to a Receive Task which wait for a signal, if the signal is not received within time limt then time out occurs. We have thousands of processes running at a time. But strangely for some of the processes timers are

Re: Weird Activiti Timer Boundary Event Behavior

tradus_yogesh — Sun, 30 Jun 2013 15:08:28 GMT

I have checked entires in the ACT_RU_JOB as well, despite right timestamp value time out didn't happen. Since there are lot of processes it is quite possible that job executor misses out some of the open jobs. Each job runs for days infact. We have 2 server instances running pointing to a common database. My understanding is that either I need to add one more server innstance so that another job executor can handle the jobs as well. Also I may need to index the DB as well because it is increasing rapidly. If this is the case as well then also tell for which column should I index the ACT_RU_JOB table. Also tell any other table that would need to be indexed as well. Also please tell what could be other possible solutions as well if this is not the case. I am using Activiti 12.1.

Thanks.

Re: Weird Activiti Timer Boundary Event Behavior

jbarrez — Mon, 01 Jul 2013 08:50:50 GMT

> Since there are lot of processes it is quite possible that job executor misses out some of the open jobs.

That can't happen in theory. The algorithm can't leave a job in the database UNLESS it has failed and it has retried it 3 times. Did you check the value of the RETRY column?

> Each job runs for days infact.

I hope that doesn't mean the logic doesn't take days to complete?

Re: Weird Activiti Timer Boundary Event Behavior

tradus_yogesh — Mon, 01 Jul 2013 17:27:13 GMT

So if job executor doesn't misses out the jobs then is it possible that it may execute it at a later stage. Because what I have observed is that they are timimg out after few hours and some after days from the scheduled time. Each timer is generally scheduled for 4-6 days. Please let me know if this could be a possibility and what could be possible solution.

Re: Weird Activiti Timer Boundary Event Behavior

tradus_yogesh — Tue, 02 Jul 2013 03:30:55 GMT

We have also noticed that there has been huge increase in CPU utilization and lot of database queries from Activiti. Primarily this is from ACT_RU_JOB where it queries to acquire jobs.

Re: Weird Activiti Timer Boundary Event Behavior

trademak — Wed, 03 Jul 2013 09:45:53 GMT

Yes, Activiti does a query to look for jobs. When there are jobs it will look for new jobs by default after 5 seconds. So if you have a lot of jobs you will have a lot of queries. What do you mean with "timing out after a few hours"? You schedule each timer to run after 4-6 days? Can you answer Joram's questions?

Best regards,