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.

Regression. Timer variable not resolved 5.8 -> 5.9

mikfreeman

Hi,
Huge Activiti fan but I'm stumped by this one. I'm using a "ProcessConfig" class to look up various properties.
However following an upgrade from 5.8 to 5.9 the below configuration no longer works.
The timeDuration property in the Timer event is not resolved and as a result the Timer is effectively ignored.

<intermediateCatchEvent id="timerintermediatecatchevent3" name="Wait for Collection">
  <timerEventDefinition>
    <timeDuration>PT${processConfig.getDuration('timeBetweenTasks')}S</timeDuration>
  </timerEventDefinition>
</intermediateCatchEvent>
‍‍‍‍‍‍

Setting the "timeBetweenTasks" directly as a variable without using the "processConfig" class works.

<intermediateCatchEvent id="timerintermediatecatchevent3" name="Wait for Collection">
  <timerEventDefinition>
    <timeDuration>PT${timeBetweenTasks}S</timeDuration>
  </timerEventDefinition>
</intermediateCatchEvent>
‍‍‍‍‍‍

Any ideas on how to resolve this?

Thanks

Michael

Find more posts tagged with

Comments

trademak

Hi Michael,

Would it be possible to create a test case for this, so I can run it myself?
Maybe create a JIRA and attach the test case.

Thanks,

mikfreeman

Hi,
I have been trying to recreate. But I can't get a simple unit test to make it past the timer. I have attached an example that uses the PluggableActivitiTestCase.

Not sure what I'm doing wrong here.

If you take the timer out the test passes

TimerIssue.zip

trademak

Hi,

I tried to reproduce it, but it's working fine for me.
I attached my test case.

Best regards,

mikfreeman

Hi,
Thanks for taking the time to respond and for your patience. Could you help me understand why the second version of the test fails?

This version passes.

public class TimerIssueTest extends PluggableActivitiTestCase {<br><br>&nbsp; @Deployment(resources="TimerIssueTest.testTimerIssue.bpmn20.xml")<br>&nbsp; public void testTimerIssue() {<br>&nbsp;&nbsp;&nbsp; Map<String, Object> variables = new HashMap<String, Object>();<br>&nbsp;&nbsp;&nbsp; variables.put("test", "2");<br>&nbsp;&nbsp;&nbsp; ProcessInstance processInstance = runtimeService<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .startProcessInstanceByKey("TimerIssueTest", variables);<br><br>&nbsp;&nbsp;&nbsp; Task task = taskService.createTaskQuery().taskName("Complete Order")<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .singleResult();<br>&nbsp;&nbsp;&nbsp; assertEquals("Complete Order", task.getName());<br><br>&nbsp;&nbsp;&nbsp; taskService.complete(task.getId());<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; JobQuery jobQuery = managementService.createJobQuery().processInstanceId(processInstance.getId());<br>&nbsp;&nbsp;&nbsp; assertEquals(1, jobQuery.count());<br>&nbsp;&nbsp;&nbsp; Calendar nowCal = new GregorianCalendar();<br>&nbsp;&nbsp;&nbsp; nowCal.add(Calendar.MINUTE, 1);<br>&nbsp;&nbsp;&nbsp; ClockUtil.setCurrentTime(nowCal.getTime());<br>&nbsp;&nbsp;&nbsp; waitForJobExecutorToProcessAllJobs(10000L, 1000L);<br>&nbsp;&nbsp;&nbsp; Task task2 = taskService.createTaskQuery().taskName("Send Order").singleResult();<br>&nbsp;&nbsp;&nbsp; assertNotNull(task2);<br>&nbsp;&nbsp;&nbsp; assertEquals("Send Order", task2.getName());<br><br>&nbsp;&nbsp;&nbsp; taskService.complete(task2.getId());<br><br>&nbsp; }<br>&nbsp; <br>}

I would expect this test to wait for 60 seconds before completing. However it immediately fails on the assertNotNull for task2

public class TimerIssueTest extends PluggableActivitiTestCase {<br><br>&nbsp; @Deployment(resources="TimerIssueTest.testTimerIssue.bpmn20.xml")<br>&nbsp; public void testTimerIssue() {<br>&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Calendar nowCal = new GregorianCalendar();&nbsp; //Using the current time<br>&nbsp;&nbsp;&nbsp; ClockUtil.setCurrentTime(nowCal.getTime());<br>&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; Map<String, Object> variables = new HashMap<String, Object>();<br>&nbsp;&nbsp;&nbsp; variables.put("test", "60");//Wait for 60 seconds<br>&nbsp;&nbsp;&nbsp; ProcessInstance processInstance = runtimeService<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .startProcessInstanceByKey("TimerIssueTest", variables);<br><br>&nbsp;&nbsp;&nbsp; Task task = taskService.createTaskQuery().taskName("Complete Order")<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .singleResult();<br>&nbsp;&nbsp;&nbsp; assertEquals("Complete Order", task.getName());<br><br>&nbsp;&nbsp;&nbsp; taskService.complete(task.getId());<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; JobQuery jobQuery = managementService.createJobQuery().processInstanceId(processInstance.getId());<br>&nbsp;&nbsp;&nbsp; assertEquals(1, jobQuery.count());<br>//&nbsp;&nbsp;&nbsp; Calendar nowCal = new GregorianCalendar();<br>//&nbsp;&nbsp;&nbsp; nowCal.add(Calendar.MINUTE, 1);<br>//&nbsp;&nbsp;&nbsp; ClockUtil.setCurrentTime(nowCal.getTime());<br>&nbsp;&nbsp;&nbsp; waitForJobExecutorToProcessAllJobs(70000L, 1000L); //Wait for 70 seconds<br>&nbsp;&nbsp;&nbsp; Task task2 = taskService.createTaskQuery().taskName("Send Order").singleResult();<br>&nbsp;&nbsp;&nbsp; assertNotNull(task2);<br>&nbsp;&nbsp;&nbsp; assertEquals("Send Order", task2.getName());<br><br>&nbsp;&nbsp;&nbsp; taskService.complete(task2.getId());<br><br>&nbsp; }<br>&nbsp; <br>}

trademak

Hi,

The idea of this unit test is to set the ClockTime after the time the timer job needs to fire.
Then the waitForJobExecutorToProcessAllJobs will execute these jobs.
If you don't include the time addition, you'll run into an endless Thread sleep.

Best regards,

mikfreeman

Hi Tijs,
Thanks again. The issue we are having seems to happen for timers with a wait time below 5 seconds. With a wait time of 5 seconds or above the timers wait (We have 4 timers in total, generally after a script task).

If the time is less than 5 seconds it seems to ignore them (We had the time set to PT3S)

The following code in the JobManager class seems to confirm this. The waitTimeInMillis is 5 seconds (Confirmed when debugging)

&nbsp;&nbsp;&nbsp; // Check if this timer fires before the next time the job executor will check for new timers to fire.<br>&nbsp;&nbsp;&nbsp; // This is highly unlikely because normally waitTimeInMillis is 5000 (5 seconds)<br>&nbsp;&nbsp;&nbsp; // and timers are usually set further in the future<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; JobExecutor jobExecutor = Context.getProcessEngineConfiguration().getJobExecutor();<br>&nbsp;&nbsp;&nbsp; int waitTimeInMillis = jobExecutor.getWaitTimeInMillis();<br>&nbsp;&nbsp;&nbsp; if (duedate.getTime() < (ClockUtil.getCurrentTime().getTime()+waitTimeInMillis)) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hintJobExecutor(timer);<br>&nbsp;&nbsp;&nbsp; }

No idea why this does not cause the same issue in 5.8.

Should I raise a defect?

Thanks again

Michael