https://answers.axonivy.com/questions/720/how-does-an-eventbean-act-in-a-cluster<p>We do some broadcast calls from plain Java, with an self written EventSubscriber for Event Start elements. This EventSubscriber catches an identifier and works fine in the Designer. It looks to works fine on the server as well. The EventSubscriber extends <code>AbstractProcessStartEventBean</code> which extends <code>IProcessStartEventBean</code>.</p> <p>Is this also works correctly when we run the server as a cluster? We expect that the event is starting just ones.</p>enFri, 30 May 2014 08:15:42 -0400https://answers.axonivy.com/questions/720/how-does-an-eventbean-act-in-a-cluster/724<p>Taken from <a href="http://bit.ly/1tsXJJD">Ivy Document</a>:</p> <blockquote> <p>How Process Start Event Beans work on a Xpert.ivy Cluster Server</p> <p>A Xpert.ivy Cluster Server consists of multiple server instances (nodes) that are running on different machines.</p> <p><strong>Normally process start event beans are instantiated on every node but only started on the master node. This guarantees that for each Event Start process element only one bean is running, no matter what the total number of nodes in the cluster server is.</strong></p> <p>However, if you need your process start event bean to be started on all cluster nodes, you may instruct the server to do so. Just have your bean class implement the (empty) marker interface IMultiNodeCapable and the above restriction will no longer apply.</p> <p>Please be aware of the fact that having multiple running instances of the same bean may lead to race conditions.</p> </blockquote> <p>Your <code>EventSubscriber</code> will work only on Master Node and instantiated once. If you have multiple <code>ProcessModelVersion</code> in your system, then the Ivy Server will guarentee only the <code>EventSubscriber</code> of the active PMV is running.</p>Genzer HawkerFri, 30 May 2014 08:15:42 -0400https://answers.axonivy.com/questions/720/how-does-an-eventbean-act-in-a-cluster/724