Hi,
I have a strange situation I’m trying to diagnose.
I have a process with an async-before on the start task.
When I start the process using the TaskList “Start process”, it takes up to a minute to have a job executor on an engine machine pick up the job and run.
I figured out that it always starts on exactly the minute boundary.
For example, if I start the process at 06:33, it will wait until 07:00 to pick up the job and continue.
Or if I start it at 59 seconds after a minute, it will wait only one second, etc…
I noticed that as soon as I start the job, it creates a row in ACT_RU_JOB, but that row is not acted upon until the minute boundary. The LOCK_EXP_TIME is set to null in the row.
Any ideas? Obviously, I just want the process to start right away, not take up to a minute.
I’m using 7.4, and here are my job-executor properties:
<job-executor>
<job-acquisition name="default">
<properties>
<property name="lockTimeInMillis">300000</property>
<property name="waitTimeInMillis">3000</property>
<property name="maxJobsPerAcquisition">3</property>
</properties>
</job-acquisition>
Thanks,
Galen