6 Replies Latest reply on Oct 18, 2007 11:20 AM by Albrecht Olivier

    Timer persisted but not fired

    ngeadah Newbie

      Hi All!

      I'm facing a frustrating timer problem. My process enters the "waitForAR" state correctly and a timer entry is correctly persisted in JBPM_TIMER, with a correct due date. My problem is the timer is never "fired" and the transition thus never followed...

      The empty action (with a space between the open and close tag) is a suggestion I already received but it did not work.

      I'm not sure what I could be missing. Perhaps a scheduler is not there monitoring the process. Is there an easy way to tell?

      <?xml version="1.0" encoding="UTF-8"?>
      
      <process-definition name="myprocess">
       <start-state name="start">
       <transition name="" to="isARAvailable"></transition>
       </start-state>
       <end-state name="end"></end-state>
      
       <state name="waitForAR">
       <timer name="waitingForAR" duedate="30 seconds" transition="waitingForARInLoop">
       <action> </action>
       </timer>
       <transition name="waitingForARInLoop" to="isARAvailable"/>
       </state>
      
       <decision name="isARAvailable" expression="#{ARChecker.isARAvailable}">
       <transition name="false" to="waitForAR"></transition>
       <transition name="true" to="writeToAR"></transition>
       </decision>
      
       <task-node name="writeToAR">
       <transition name="writeToAR" to="end">
       <action expression="#{ARReturnService.writeToAR}"/>
       </transition>
       </task-node>
      </process-definition>