search

plexiti / camunda-grails-plugin

Integrates Camunda BPM with the Grails framework.
http://grails.org/plugin/camunda
Apache License 2.0
18 stars 8 forks source link

Execution of start timer events #25

Closed behrad closed 9 years ago

behrad commented 9 years ago

My start timer events are not being executed... I was unable to check if Job Executor is started by grails plugin, or where could be my problem!? My createJobQuery().list() returns

[TimerEntity[repeatR/2014-09-08T01:00:00/PT24H, id=16008, revision=1, duedate=Mon Sep 15 01:00:00 IRDT 2014, lockOwner=null, lockExpirationTime=null, executionId=null, processInstanceId=null, isExclusive=true, retries=3, jobHandlerType=timer-start-event, jobHandlerConfiguration=nightlyBill, exceptionByteArray=null, exceptionByteArrayId=null, exceptionMessage=null, deploymentId=null], TimerEntity[repeat0 53 12 * * ?, id=16022, revision=1, duedate=Sun Sep 14 12:53:00 IRDT 2014, lockOwner=null, lockExpirationTime=null, executionId=null, processInstanceId=null, isExclusive=true, retries=3, jobHandlerType=timer-start-event, jobHandlerConfiguration=testProcess, exceptionByteArray=null, exceptionByteArrayId=null, exceptionMessage=null, deploymentId=null]]

martinschimak commented 9 years ago

Hi @behrad I assume that this is not related to the plugin, but a camunda configuration question.

However, please be aware that during integration test phase of any grails environment, two camunda configuration values are set by the plugin: the camunda job executor is turned off and service mocking is made available. This could explain what you observe? This is explained in more detail in section testing of the plugin guide. Please reopen this issue if you feel to see a plugin related behaviour.