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.

BPM Timer Expiry

samsmith

Hi,

I have got a BPM process that has got an 'Timer Intermediate Catch Event' with duration set to 10 seconds [PT10S].
When I try to unit test the BPM process, I noticed that the timer doesn't get expired at all. 'asyncExecutorActivate' property is set to true.

But when I write the following code in my unit test, then the timer does get expired after 10 seconds.

JobQuery jobQuery = processEngine.getManagementService().createJobQuery().processInstanceId(processInstance.getId());
Date startTime = new Date();
processEngine.getProcessEngineConfiguration().getClock().setCurrentTime(new Date(startTime.getTime() + (10 * 1000) + 1000));
JobTestHelper.waitForJobExecutorToProcessAllJobs(processEngine.getProcessEngineConfiguration(), processEngine.getManagementService(), 10000L, 25L);
assertEquals(0L, jobQuery.count());

My question is that why do I have to write the above code for the timer to work from my unit test.

Thanks

Find more posts tagged with

Comments

martin_grofcik

Hi Sam,

explanation could be

<br>&nbsp; public static void waitForJobExecutorToProcessAllJobs(ProcessEngineConfiguration processEngineConfiguration, <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ManagementService managementService, long maxMillisToWait, long intervalMillis, boolean shutdownExecutorWhenFinished) {<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; JobExecutor jobExecutor = null;<br>&nbsp;&nbsp;&nbsp; AsyncExecutor asyncExecutor = null;<br>&nbsp;&nbsp;&nbsp; if (processEngineConfiguration.isAsyncExecutorEnabled() == false) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jobExecutor = processEngineConfiguration.getJobExecutor();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jobExecutor.start();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; } else {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; asyncExecutor = processEngineConfiguration.getAsyncExecutor();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; asyncExecutor.start();<br>&nbsp;&nbsp;&nbsp; }<br><br>

Regards
Martin

samsmith

Hi Martin,

When I test my code in tomcat using Activiti - Explorer, then the timer does expire automatically after 10 seconds, but in my junit, I have to write a snippet of code. Are you implying that in tomcat, the 'asyncExecutor' is automatically started on the server start whereas in J-Unit, I start the 'asyncExecutor' by calling the below code:

JobTestHelper.waitForJobExecutorToProcessAllJobs(processEngine.getProcessEngineConfiguration(), processEngine.getManagementService(), 10000L, 25L);

Thanks

martin_grofcik

Hi Sam,

it all depends on your process engine configuration. (By default job executor is not started in jUnit test)

Regards
Martin