topic Re: Exclusive gateway behaviour during JVM crash in Alfresco Archive

Exclusive gateway behaviour during JVM crash

lakmg — Fri, 01 Feb 2013 09:46:08 GMT

Hi,I have an application which uses activiti, my model is as below:user Task –>service Task—>exclusiveGwy–>serviceTask–>UserTask—I would like to know the state of ACT_ID_ for the following scenario: when my application is at exclusiveGwy, if the JVM crashes, what will be stored in the c

Re: Exclusive gateway behaviour during JVM crash

frederikherema1 — Fri, 01 Feb 2013 09:56:18 GMT

When your JVM craches when the process was running (eg. currently in the gateway-step) the DB-transaction that was active will NOT be committed. When the engine boots again, the process state will be the same as before the API-call (in your case, the usertaks you completed during the crash, will still be there uncompleted).

All acitviti-related process-logic is rolled back, together with all of your DB-mutations, if these participate in the same transaction.

Re: Exclusive gateway behaviour during JVM crash

lakmg — Fri, 01 Feb 2013 10:13:22 GMT

Hi,

Thanks for the quick reply.

One more confirmation needed is:
If at servicetask JVM crashes, even for this it goes back to userTask, is my understanding correct?

Thanks,
Lakshmi

Re: Exclusive gateway behaviour during JVM crash

frederikherema1 — Fri, 01 Feb 2013 10:17:04 GMT

Yes, that is correct. As long as the process doesn't reach a wait-state, async task or process-end, the transaction is not committed. So if JVM crashes (or an exception is thrown) in one of your steps between the two userTasks, it's rolled back to the state it was before, waiting in userTask1.