nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Behaviour in case of failure

rodolfobarbeiro

Hello activiti-team!

I'm using Activiti for some time and would like to know what happens in the following cases:

What the behavior of Activiti in case of failure (SO crash, hardware shutdown…)?

What happens to the instances of processes? They will be restored?

Thanks!

Find more posts tagged with

Comments

ronald_van_kuij

Transactions that were not commited will be either rolled back or commited, depending on the transaction manager and the actual state it is in. If you do. Not use 2pc/xa it will simple, in other cases it really depends on the TM, databease used etc. In fact this is no different than any other app using db's

rodolfobarbeiro

Still got questions…

Look my scenario:

1 - Acitiviti running.
2 - There are 50 instances of process assets. Running.
3 - The OS crashes.

I am not referring to what happens to the database (although they are directly related).

I wonder if, after recovery of the OS, the 50 instances of the processes continue to run from the stopping point.

My question is regarding the loss of the execution context of processes. The process instances will be lost?

I hope it was clear this time…

Thanks for your reply!

ronald_van_kuij

things 'triggered' via Activiti jobs/timers fill be automatically triggered again in the 'correct context' Things done via a ui must be re-done via the ui. Things triggered from external systems must be triggered via external systems again. So still nothing special compared to other applications/framework.