nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How to specify/increase termination timeout

suribabu

Hi,

I am new bee to Activiti BPM. When I am trying to start my process instance using

ProcessInstance processInstance = runtimeService.startProcessInstanceByKey("process1",map);

(this process includes many jobs run in parallel),
the process is getting terminated after 60 seconds without completing all my jobs. (see error msg below

org.activiti.engine.impl.jobexecutor.DefaultJobExecutor stopExecutingJobs
WARNING: Timeout during shutdown of job executor. The current running jobs could not end within 60 seconds after shutdown operation.

I did not set this time any where in config xml. If this is the default behavious, how can I change this?
Is there any parameter to increase this timeout ?
Please suggest.

Thanks in advance.

-Suri

Find more posts tagged with

Comments

jbarrez

(this process includes many jobs run in parallel),

What do you mean with this? Does it have a lot of timers? Does it have many async steps?

Can you reproduce the issue in an easy unit test?

suribabu

Hi jbarrez,

It doesn't have timers but it has many async steps.
Here is the serviceTask configuration:

<serviceTask id="servicetask1" name="Process SubProj List" activiti:expression="${ProcessSubProjects.processSubProjects(cardSubProject,execution)}" activiti:async="true" activiti:exclusive="false">
<multiInstanceLoopCharacteristics isSequential="false" activiti:collection="CardSubProjectList" activiti:elementVariable="cardSubProject">
</multiInstanceLoopCharacteristics>
</serviceTask>

Thanks,
Suri.

jbarrez

On what database are you running on? Does your database use table locks? Because that's the only reason I can quickly think of that would generate timeouts.

frederikherema1

If there are jobs with a duration that exceed that 60 seconds, these will be "killed" when the job-executor is requested to shut down and not finished within 60 seconds.

This is built in into the job executor. However, by extending and plugging in your own JobExecutor, you can later this behavior and have a longer wait-time or other behavior.

See src.main.java.org.activiti.engine.impl.jobexecutor.DefaultJobExecutor

<br> protected void stopExecutingJobs() {<br>&nbsp;&nbsp;&nbsp; stopJobAcquisitionThread();<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; // Ask the thread pool to finish and exit<br>&nbsp;&nbsp;&nbsp; threadPoolExecutor.shutdown();<br><br>&nbsp;&nbsp;&nbsp; // Waits for 1 minute to finish all currently executing jobs<br>&nbsp;&nbsp;&nbsp; try {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if(!threadPoolExecutor.awaitTermination(60L, TimeUnit.SECONDS)) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; log.log(Level.WARNING, "Timeout during shutdown of job executor. "<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + "The current running jobs could not end within 60 seconds after shutdown operation.");&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; } catch (InterruptedException e) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; log.log(Level.WARNING, "Interrupted while shutting down the job executor. ", e);<br>&nbsp;&nbsp;&nbsp; }<br><br>&nbsp;&nbsp;&nbsp; threadPoolExecutor = null;<br>&nbsp; }<br>