If you are using a JBoss clustered installation of LiveCycle ES2 to handle batches of events, you may notice that some events are received twice, (i.e. 10 events thrown, 12 events received).
This can occur if the JBoss cluster is not configured correctly. In the cluster settings (i.e. run.bat for JBoss) it is important to give each node in the cluster a unique server name using the “Adobeidp.serverName” parameter. For example, Adobeidp.serverName=server1 for the first node in the cluster, and Adobeidp.serverName=server2 for the second node and so on…
- JBoss documentation: http://help.adobe.com/en_US/livecycle/9.0/clustering_jboss.pdf#page=19
- WebSphere and WebLogic do not require this parameter for the JVM as the cluster nodes are managed from the application server administration consoles
When you give the two servers in a cluster the same name, you wind up with a workmanager on each server that has the same name. Work items get assigned to a specific workmanager, but since they both have the same name it becomes a race to see which one picks up the work item first. In some specific timing cases both will pick up the work item at the same time and process it, which is the reason for the duplication of events.