AnsweredAssumed Answered


Question asked by derikalov on Feb 20, 2013
Latest reply on May 6, 2014 by schitale
I know that Activiti is "just a jar" but what happens if there are N instances (JVMs) running against the same Activiti db?
What if I want to achieve some load-balancing and fault tolerance?

Is there an easy way to achieve that? I think that everything except timerEvent-triggered processes can be cleanly split across N engines. But for timerEvent triggered jobs, can I have some hooks into the engine so it first does some kind of election of which engine picks up the process - and the other engines then ignore it.