0 Replies Latest reply on Feb 29, 2012 7:32 AM by liliana.iovanovici

    Resume a process after a crash

    liliana.iovanovici Newbie

      I read the documentation about persistence and process recovery:


      "If you configure the engine to use persistence, it will automatically store the runtime state into the database. You do not have to trigger persistence yourself, the engine will take care of this when persistence is enabled. Whenever you invoke the engine, it will make sure that any changes are stored at the end of that invocation, at so-called safe points. Whenever something goes wrong and you restore the engine from the database, you also should not reload the process instances and trigger them manually to resume execution, as process instances will automatically resume execution if they are triggered, like for example by a timer expiring, the completion of a task that was requested by that process instance, or a signal being sent to the process instance. The engine will automatically reload process instances on demand.


      And I have some questions:


      1. If I have a process: Start - Timer1- Script1- Timer2- Script2 -Stop and my process crash at Timer1 or Timer2, the jBPM engine will know to automatically to continue this process, and the tasks will be executed, without some thrird party mechanism (which look in databases and get session and process id and send some events) ?


      2.  The jBPM5 engine can be embeded or must be deployed standalone to do process recovery?


      3. I dont't understand what means "The engine will automatically reload process instances on demand". If is "on demand" - is still "automatically" ?