2 Replies Latest reply on Jul 20, 2009 10:41 AM by kukeltje

    JBPM 3.2.2 Timer Example

    csplrj1

      JBPM 3.2.2 Timer

      I am trying a timer on JBPM 3.2.2 but it seems its not working somehow.
      A Entry in JBPM_JOB table is passed but the time specified seems to be wrong or taken from somewhere which I don't understand from where it has been taken

      The below is the part of processDefinition which does not works?

      The Time in the JBPM_JOB table is "7/20/2009 9:06:10 AM" though on my local machine time is around "7/20/2009 2:30PM"

      Thanks in advance

      CSJakharia

      I have entry as
      <task-node name="legalDept">






      com.zycus.contract.authoring.process.ContractStageUpdateEvent1





      System.out.println(&quot;Timer Fired&quot;);








      </task-node>

        • 1. Re: JBPM 3.2.2 Timer Example
          csplrj1

          The XML is not being displayed properly and so the correct XML is

          <task-node name="legalDept">
           <task name="task3">
           <assignment class="com.process.jbpm.ActorAssignmentHandler"></assignment>
           </task>
           <event type="task-assign">
           <action class="com.process.jbpm.JbpmActionListener">
           <actionListener>
           com.zycus.contract.authoring.process.ContractStageUpdateEvent1
           </actionListener>
           </action>
           </event>
           <timer name="timer1" transition="LegalApprove" duedate="3 business minutes">
           <script>
           System.out.println("Timer Fired");
           </script>
           </timer>
           <transition to="join2" name="LegalApprove">
           <action class="com.process.jbpm.JbpmPollingActionListener"></action>
           </transition>
           <transition to="join2" name="raiseSomeConcern">
           <action class="com.process.jbpm.JbpmPollingActionListener"></action>
           </transition>
           </task-node>


          • 2. Re: JBPM 3.2.2 Timer Example
            kukeltje

            I have no clue about the dates, but I think it is better to first try with 3.2.6sp1 and see if the problem is still there. Also look in the console to see the info about jobs