Timers are not deleted after workflow completion causing performance issues

mreyem — Fri, 09 Aug 2013 12:43:26 GMT

Hi,I've developed a workflow using Activiti and Alfresco 4.2 that uses some timers (of type TimerCatchingEvent). Every time a timer fires a new entry is created in the ACT_RU_JOB table of Activiti, but I've read from the Activiti forums that this is the expected behaviour. The problem is that after

Re: Timers are not deleted after workflow completion causing performance issues

jservajean — Thu, 06 Mar 2014 09:14:41 GMT

Hi

I had the same kind of problem.
I would use a boundaryevent to set a timer on a validation task (I wanted the files to be archived at a further date after the validation done).

<blockcode>
    <boundaryEvent id="validationTaskBoundarytimer" name="" cancelActivity="true" attachedToRef="validationTask">
      <timerEventDefinition>
        <timeDate>${wmase_dueDate}</timeDate>
      </timerEventDefinition>
    </boundaryEvent>
</blockcode>

My first way of achieving this was to set an

executionListener‍

on the

sequenceFlow‍

wiring the boundaryEvent with the endEvent, and do all the copying stuff in it.
Well, the code would execute but the files remained in the same place and the timer job still there too.
In other words, the transaction was never commited !

I solved the issue by plaing my script in a new javascript task (

<serviceTask id="archivageTask" name="Archivage" activiti:class="org.alfresco.repo.workflow.activiti.script.AlfrescoScriptDelegate">‍

) between the boundaryEvent and the endEvent, and it turned out to work (don't ask me why…) !

Hope it helps.

topic Re: Timers are not deleted after workflow completion causing performance issues in Alfresco Archive

Timers are not deleted after workflow completion causing performance issues

Re: Timers are not deleted after workflow completion causing performance issues