topic Re: Simple flow with Timer not repeating in Alfresco Archive

Simple flow with Timer not repeating

castyn — Tue, 15 Sep 2015 23:44:15 GMT

Hello all, I have a fairly simply process setup that gets an object, performs some logic via JavaDelegate tasks, and repeats if the process did not go through properly. There is a 10 second wait as well. What I am observing happening is that after the notifySupervisorTask, the process exists and d

Re: Simple flow with Timer not repeating

castyn — Wed, 16 Sep 2015 23:18:04 GMT

A bit of follow up, I have the following beans configured as well. When I remove the timer, the process completes as expected, just without the desired delay. Seems like it should be the most simple case ever, but for some reason the process bails out (without any exceptions or warnings) with that timer there

<code>
<bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
    <property name="targetDataSource">
      <bean class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
        <property name="driverClass" value="org.h2.Driver" />
        <property name="url" value="jdbc:h2:mem:activiti;DB_CLOSE_DELAY=1000" />
        <property name="username" value="sa" />
        <property name="password" value="" />
      </bean>
    </property>
</bean>

<bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
    <property name="dataSource" ref="dataSource" />
</bean>

<bean id="asyncExecutor" class="org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor">
    <property name="defaultAsyncJobAcquireWaitTimeInMillis" value="1000" />
    <property name="defaultTimerJobAcquireWaitTimeInMillis" value="1000" />
</bean>

<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
    <property name="dataSource" ref="dataSource" />
    <property name="transactionManager" ref="transactionManager" />
    <property name="databaseSchemaUpdate" value="true" />
    <property name="jobExecutorActivate" value="true" />
    <property name="asyncExecutor" ref="asyncExecutor" />
    <property name="asyncExecutorEnabled" value="true" />
    <property name="asyncExecutorActivate" value="false" />
</bean>

<bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean">
    <property name="processEngineConfiguration" ref="processEngineConfiguration" />
</bean>

<bean id="runtimeService" factory-bean="processEngine" factory-method="getRuntimeService" />
</code>

Re: Simple flow with Timer not repeating

castyn — Fri, 18 Sep 2015 01:44:44 GMT

I have tried everything I can think of, pointing out that I am new to activiti. I created a simple flow of task -> timer -> task, and after the timer the flow stops. I have altered the configuration on the process engine through about every iteration of executor vs async executor enabling and disabling. I am not sure what else I can try at this point.

Re: Simple flow with Timer not repeating

martin_grofcik — Tue, 22 Sep 2015 06:36:55 GMT

Hi Castyn,

have a look on the following jUnit test in the activiti source:
org.activiti.engine.test.bpmn.event.timer.IntermediateTimerEventTest#testCatchingTimerEvent

In the case when it does not work, create jUnit test:
http://forums.activiti.org/content/sticky-how-write-unit-test

Regards
Martin

Re: Simple flow with Timer not repeating

castyn — Wed, 23 Sep 2015 13:09:57 GMT

This is largely for a proof of concept as we are evaluating a number of BPMN engines so I haven't had the time to devote to pulling out the base case of a catch timer into a unit test. Also, that unit test as far as I can tell does not actually leverage a BPMN.xml or non default configuration and instead is just testing the underlying java code, which works. This unit tests run fine when deployed and I have run all of the examples within the container as well. I believe it is related to configuration that is likely causing the issue, and unit tests, at least in my experience, are poor representations of server side configuration issues and challenges.

I'll keep trying to pull it apart and can try to create an integration test (don't think unit will cut it for a task -> timer -> task example with custom config). But my hopes are not very high at this point of having a breakthrough on the issue. I may end up having to debug through the source code of the engine to understand why a timer catch event just ends an activiti process without any log message.

Re: Simple flow with Timer not repeating

martin_grofcik — Thu, 24 Sep 2015 06:58:38 GMT

Hi Castyn,

The unit test org.activiti.engine.test.bpmn.event.timer.IntermediateTimerEventTest#testCatchingTimerEvent uses following bpmn20 process model:


<?xml version="1.0" encoding="UTF-8"?>
<definitions id="definitions" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:smileysurprised:mgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns:smileysurprised:mgdi="http://www.omg.org/spec/DD/20100524/DI"
             xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
             xmlns:activiti="http://activiti.org/bpmn"
             targetNamespace="Examples">

    <process id="intermediateTimerEventExample" name="Timer intermediate event example">

        <startEvent id="theStart"/>
        <sequenceFlow id="flow1" sourceRef="theStart" targetRef="timer"/>

        <intermediateCatchEvent id="timer">
            <timerEventDefinition>
                <timeDuration>PT5M</timeDuration>
            </timerEventDefinition>
        </intermediateCatchEvent>

        <sequenceFlow id="flow2" sourceRef="timer" targetRef="theEnd"/>

        <endEvent id="theEnd"/>

    </process>
    <bpmndi:BPMNDiagram id="diagram">
       <bpmndi:BPMNPlane bpmnElement="intermediateTimerEventExample" id="intermediateTimerEventExample_di">
          <bpmndi:BPMNShape bpmnElement="theStart" id="theStart_di">
             <omgdc:Bounds height="30.0" width="30.0" x="114.0" y="185.0"/>
          </bpmndi:BPMNShape>
          <bpmndi:BPMNShape bpmnElement="timer" id="timer_di">
             <omgdc:Bounds height="30.0" width="30.0" x="195.0" y="185.0"/>
          </bpmndi:BPMNShape>
          <bpmndi:BPMNShape bpmnElement="theEnd" id="theEnd_di">
             <omgdc:Bounds height="28.0" width="28.0" x="270.0" y="186.0"/>
          </bpmndi:BPMNShape>
          <bpmndi:BPMNEdge bpmnElement="flow1" id="flow1_di">
             <omgdi:waypoint x="144.0" y="200.0"/>
             <omgdi:waypoint x="195.0" y="200.0"/>
          </bpmndi:BPMNEdge>
          <bpmndi:BPMNEdge bpmnElement="flow2" id="flow2_di">
             <omgdi:waypoint x="225.0" y="200.0"/>
             <omgdi:waypoint x="270.0" y="200.0"/>
          </bpmndi:BPMNEdge>
       </bpmndi:BPMNPlane>
    </bpmndi:BPMNDiagram>

</definitions>

activiti engine configuration is:


<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans   http://www.springframework.org/schema/beans/spring-beans.xsd">

  <bean id="processEngineConfiguration"
    class="org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration">

   <property name="jdbcUrl" value="jdbc:h2:mem:activiti;DB_CLOSE_DELAY=1000" />
   <property name="jdbcDriver" value="org.h2.Driver" />
   <property name="jdbcUsername" value="sa" />
   <property name="jdbcPassword" value="" />

    <!– Database configurations –>
    <property name="databaseSchemaUpdate" value="drop-create" />

    <!– job executor configurations –>
    <property name="jobExecutorActivate" value="false" />
    <property name="asyncExecutor" ref="asyncExecutor" />
    <property name="asyncExecutorEnabled" value="true" />
    <property name="asyncExecutorActivate" value="false" />
    
    <property name="defaultFailedJobWaitTime" value="1" />
    <property name="asyncFailedJobWaitTime" value="1" />

    <!– mail server configurations –>
    <property name="mailServerPort" value="5025" />
    
    <property name="mailServers">
      <map>
        <entry key="myEmailTenant">
          <bean class="org.activiti.engine.cfg.MailServerInfo">
            <property name="mailServerHost" value="localhost" />
            <property name="mailServerPort" value="5025" />
            <property name="mailServerUseSSL" value="false" />
            <property name="mailServerUseTLS" value="false" />
            <property name="mailServerDefaultFrom" value="activiti@myTenant.com" />
            <property name="mailServerUsername" value="activiti@myTenant.com" />
            <property name="mailServerPassword" value="password" />
          </bean>
        </entry>
      </map>
    </property>
    
    <property name="history" value="full" />
  </bean>
  
  <bean id="asyncExecutor" class="org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor">
    <property name="defaultAsyncJobAcquireWaitTimeInMillis" value="1000" />
    <property name="defaultTimerJobAcquireWaitTimeInMillis" value="1000" />
  </bean>

</beans>

What the code really does :


@Deployment// deploys model to the engine (based on the testclass.method name (IntermediateTimerEventTest.testCatchingTimerEvent.bpmn20.xml)
  public void testCatchingTimerEvent() throws Exception {

    // Set the clock fixed
    Date startTime = new Date();

    // After process start, there should be timer created
    ProcessInstance pi = runtimeService.startProcessInstanceByKey("intermediateTimerEventExample");
    JobQuery jobQuery = managementService.createJobQuery().processInstanceId(pi.getId());
    assertEquals(1, jobQuery.count());

    // After setting the clock to time '50minutes and 5 seconds', the second timer should fire
    processEngineConfiguration.getClock().setCurrentTime(new Date(startTime.getTime() + ((50 * 60 * 1000) + 5000))); // setting the time to the future (5 minutes) (yes activiti can work in virtual time)
    waitForJobExecutorToProcessAllJobs(5000L, 25L); // starts jobexecutor and process all jobs.

    assertEquals(0, jobQuery.count());
    assertProcessEnded(pi.getProcessInstanceId());
  }

I do not agree with your last comment.
In case when your case does not work, create jUnit test please.
http://forums.activiti.org/content/sticky-how-write-unit-test

Regards
Martin