How to ensure the process execution restarts along with restarting the last safe point (Human Task) even though it was completed before an Exception takes place?
Issue
- The How to handle Exception in jBPM5? article state that: "As long as you use
LocalTaskService+SyncWSHumanTaskHandler
, process instances and tasks are consistent so you will be able to continue the process from the last committed state." Considering this condition, there is a process definition which has aService Task
right after aUser Task
node and after theUser Task
node is completed when theService Task
was getting executed, aRuntimeException
takes place. In this scenario it is seen that jBPM 5 engine rolls back all transactions back to the last safe point (which is a completed Human Task node). But, how to get the process instance to start again by restarting the last safe point (Human Task) even though it was completed? If the last safe point was a message or signal event then it can send another message into the process instance to start it again. In case of running the process instance throughBusiness Central Console
will it be possible to resume the process execution in case the above scenario takes place?
Environment
- Red Hat Decision Manager / JBoss BRMS (BRMS)
- 5.3.x
- Java Business Process Model (jBPM)
- 5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.