Activiti architecture / Process Engine

[sherod]

If I have a timer task that is scheduled to execute in 35 days time, and the server is restarted numerous times in that period, does the Activiti process engine automatically reestablish the active processes in memory and ensure such triggers are run?

Or does this require the embedder to undertake the coding work to do this?

If the former, how are timer tasks which passed their due time during a server restart or offline period get handled?  Are the immediately triggered on startup?

Apologies if this is in the manual, happy to get sent a link.

[aparnachaudhary]

The timer information is persistent and maintained in ACT_RU_JOB table. The due date (DUEDATE_) is calculated based on the timeDuration specified in the event definition.

If the former, how are timer tasks which passed their due time during a server restart or offline period get handled? Are the immediately triggered on startup?

Yes they are immediately triggered on server startup.

I've updated my spring-integration prototype to demonstrate use of timer event. In the prototype, once the defect is created, you can bring down the server and bring it up after the 1min. You can see the defect is removed from the review task list, the process is terminated and moved to history table (act_hi_procinst).

http://blog.aparnachaudhary.net/2010/11/23/activiti-bpm-springintegration-mail-adapter/