topic Re: Async Job Executor only executes job after lock expiration in Alfresco Forum

Async Job Executor only executes job after lock expiration

jritter — Fri, 29 Sep 2017 14:00:53 GMT

HiWe are currently in the process of upgrading our Activiti deployment from version 6.18 to version 6.0, which includes also the new Async Job executor. While giving activiti 6 a try, I noticed something which I could not explain:The documentation says, that if the asyncExecutor for a process engine

Re: Async Job Executor only executes job after lock expiration

kam — Tue, 03 Oct 2017 21:36:48 GMT

I have had similar experience with 5.22 we use. Seems the asyncExecutorDefaultAsyncJobAcquireWaitTime config does not apply on asyncExecutor. I tried to check config.getAsyncExecutor().getDefaultAsyncJobAcquireWaitTimeInMillis() it still returns default value (10 sec) even though I set it to 2 sec. Any how, i then set it by config.getAsyncExecutor().setDefaultAsyncJobAcquireWaitTimeInMillis(2000) on startup of my application and it works. That said I yet to figure out why it would not take initial config from asyncExecutorDefaultAsyncJobAcquireWaitTime. I use spring boot version and tried to set it by processEngineConfigurationConfigurer. Hope this helps

Re: Async Job Executor only executes job after lock expiration

jritter — Fri, 06 Oct 2017 11:58:58 GMT

Hi Kamlesh

Thanks for your reply, but unfortunately this does not seem to help. I've configured the defaultASsyncJobAcquireWaitTimeInMillis parameter during the initialisation of my Spring Boot Application, but it does not seem to help. I've noticed something interesting though. It does not happen if I have two process engines, one which creates the jobs (Async Executor Disabled), and the other one executing them (Async Executor Enabled). But still, this is really strange.

Unfortunately, the rest api from where some of my workflows are launched ties itself to the executor and not the producer engine. Does anybody how I can tie the rest api to a particular workflow engine when using Spring Boot? I've marked the producerProcessEngine as primary, but that does not seem to help:

Thanks and regards,
Jürg

Re: Async Job Executor only executes job after lock expiration

haridaniel — Tue, 28 Nov 2017 20:20:50 GMT

I experienced same, and opened a stackoverflow.

Re: Async Job Executor only executes job after lock expiration

haridaniel — Thu, 30 Nov 2017 23:31:26 GMT

It seems I found a workaround to address the problem:
-Start the process in a transaction.

-Suspend the process in same transaction.

-Activate the process after transaction commit.

Implementation in spring environment:

String processInstanceId = runtimeService.startProcessInstanceByKey(processId, variableMap).getId();

runtimeService.suspendProcessInstanceById(processInstanceId);

transactionTool.afterCommit(() -> {
runtimeService.activateProcessInstanceById(processInstanceId);
});

public class TransactionTool {

public void afterCommit(Runnable runnable) {
if (TransactionSynchronizationManager.isActualTransactionActive()) {
logger.trace("Transaction exists, registering runnable after commit.");
TransactionSynchronizationManager.registerSynchronization(
new TransactionSynchronizationAdapter() {
@Override
public void afterCommit() {
logger.trace("Commit done, executing runnable.");
runnable.run();
}
});
} else {
logger.trace("Transaction not exists, executing runnable in-place.");
runnable.run();
}
}

}

Re: Async Job Executor only executes job after lock expiration

oluetkeh — Tue, 01 May 2018 23:26:50 GMT

I've done some research and provided my findings as another answer to the StackOverflow thread mentioned above Tasks marked as 'Async' and not 'Exclusive' causes the issue