topic Re: BPM Timer Expiry in Alfresco Archive

BPM Timer Expiry

samsmith — Fri, 08 Apr 2016 10:50:46 GMT

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

Re: BPM Timer Expiry

martin_grofcik — Fri, 08 Apr 2016 12:29:02 GMT

Hi Sam,

explanation could be


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

Regards
Martin

Re: BPM Timer Expiry

samsmith — Fri, 08 Apr 2016 12:46:49 GMT

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

Re: BPM Timer Expiry

martin_grofcik — Mon, 11 Apr 2016 07:09:08 GMT

Hi Sam,

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

Regards
Martin