topic Re: How to control the frequency at which ACT_RU_JOB table is being polled in Alfresco Archive

How to control the frequency at which ACT_RU_JOB table is being polled

rajeshiv — Tue, 24 Feb 2015 17:27:36 GMT

Hi,I have a work flow with an expiration timer set on it. I see that the activiti polls on the ACT_RU_JOB. I see that the below two queries are being executed every time it polls.select *from ACT_RU_JOBwhere (RETRIES_ > 0) and (DUEDATE_ is null or DUEDATE_ < :1) and (LOCK_OWNER_ is null or LOC

Re: How to control the frequency at which ACT_RU_JOB table is being polled

jbarrez — Sat, 28 Feb 2015 09:22:48 GMT

Which Activiti version? I'm assuming the latest: then those settings can be tweaked: https://github.com/Activiti/Activiti/blob/master/modules/activiti-engine/src/main/java/org/activiti/engine/impl/asyncexecutor/DefaultAsyncJobExecutor.java#L59

Re: How to control the frequency at which ACT_RU_JOB table is being polled

sridhar_b — Tue, 20 Oct 2015 13:49:05 GMT

Thanks jbarrez.

Which are the ones below need to be tweaked? Is it possible to disable the polling?

keepAliveTime = 5000L;
maxTimerJobsPerAcquisition = 1;
maxAsyncJobsDuePerAcquisition = 1;
defaultTimerJobAcquireWaitTimeInMillis = 10 * 1000;
defaultAsyncJobAcquireWaitTimeInMillis = 10 * 1000;
timerLockTimeInMillis = 5 * 60 * 1000;
asyncJobLockTimeInMillis = 5 * 60 * 1000;
retryWaitTimeInMillis = 500;

Re: How to control the frequency at which ACT_RU_JOB table is being polled

sridhar_b — Tue, 20 Oct 2015 14:38:33 GMT

I'm currently using 5.12 version. Is there a way to fix this in ver 5.12?
Thanks in advance.

Re: How to control the frequency at which ACT_RU_JOB table is being polled

jbarrez — Tue, 20 Oct 2015 17:35:55 GMT

"Is it possible to disable the polling?"

Yes, simply disable the job executor (or the asyncExecutor) on the process engine configuration.

"Which are the ones below need to be tweaked"

The acquireWaitTimeMillis are the ones used to configure the frequency of polling

"I'm currently using 5.12 version. Is there a way to fix this in ver 5.12?"

No idea anymore. 5.12 is 2,5 years old. That's ancient in software country …

Re: How to control the frequency at which ACT_RU_JOB table is being polled

sridhar_b — Wed, 21 Oct 2015 04:01:23 GMT

Thanks jbarrez. Appreciate you quick response.

Re: How to control the frequency at which ACT_RU_JOB table is being polled

sridhar_b — Fri, 30 Oct 2015 14:30:20 GMT

Hi jbarrez,

I have reduced the frequency at which these queries are executed by tweaking the setting in activiti.cfg.xml.
I un-commented the below in activity.cfg.xml to use the DefaultJobExecutor.
Also, added the property "waitTimeInMillis" to the bean and set its value to 10min.

With the above change, I am able to control the frequency of the query execution, however, I see the Retry is not functioning correctly.
I have a timer with delay of 5min between each Retry. After the first execution, it retries next 2 executions immediately and doesn't wait for the timer.

However, when I comment back the below code, it works fine. It does wait between each Retry. Please let me know if I need to do it differently.
Thanks in advance.

//Comment the block
<property name="jobExecutor">
                        <bean class="org.activiti.engine.impl.jobexecutor.DefaultJobExecutor">
                                <property name="queueSize" value="3"/>
                                <property name="corePoolSize" value="3"/>
                                <property name="maxPoolSize" value="10"/>
                                <property name="maxJobsPerAcquisition" value="30"/>
                                <property name="waitTimeInMillis" value="600000"/>
                        </bean>
</property>

Re: How to control the frequency at which ACT_RU_JOB table is being polled

sridhar_b — Fri, 30 Oct 2015 14:32:08 GMT

Re: How to control the frequency at which ACT_RU_JOB table is being polled

jbarrez — Tue, 03 Nov 2015 13:11:06 GMT

"After the first execution, it retries next 2 executions immediately and doesn't wait for the timer."

I'm not sure I'm following what you are saying here. What do you mean with 'wait for the timer'? The settings above normally don't influence the retry (as the retry is done when the job is executed, while the settings above are for acquisition).

Also note that setting it to 10 minutes won't be picking up timers that are set to 5 minutes difference ..