AnsweredAssumed Answered

System restart

Question asked by pollop on Sep 24, 2013
Latest reply on Sep 25, 2013 by pollop

I am trying to understand how Activiti handles unexpected restarts.
My company is currently assessing Activiti's hability to recover from an unexpected shutdown of the system.

The context is the following, Activiti will run on a server handling lots of process instances mainly consisting of service tasks.
If something happens to the system, a second server will handle the continuation of the application.

What I am really interested in is: what does Activiti consider as a transaction?, when is the context saved in the database? etc. Any information would be helpful.

To take a more concrete example, let's say the server crashed (for reasons outside the scope of the application.
At the time of crash, hundreds of Service Tasks were being executed.

When the system restarts, those process instances do not seem to run anymore.
I looked in the database and saw that their status is Active but they are not running.

105 2 105 null null processTriple:1:103 null servicetask2 TRUE FALSE TRUE FALSE 1 4

Is it possible for the engine to restart those tasks or do I have to do it mannually?

Thanks a lot for your help.

Note: ASYNC execution is of course activated.