Hi
just joined recently, so please excuse me if this is a repeat - I have searched the forums for relevant information, but still don't have all the information I need.
We are prototyping a BPM requirement using Activiti. The server is setup as a standalone system on tomcat, and we have a service wrapper that we use to provide an enhanced API to the system. We are very impressed with it so far, and its looking good in terms of a choice.
However, I am now trying to determine the clustering capabilities of the system. What I have understood so far is that we can easily connect multiple engines to a common database, and the job executors will correctly work to pick up work from the queues.
Where I am not clear is in the following: We have an API to start a process on an engine. This will come from a load balancer, and so the calling applications request may hit any of the engines. So the first call may hit engineB which will launch the process on serverB. The next call from the LB will hit engineA on serverA. Say that the process on engineB is sitting on a human interaction task. Before the human interaction occurs, serverB goes down. When the interaction occurs, the LB will direct the request to serverA - will this correctly continue the process?
Hope that makes sense?
Thx
Z
