How to avoid multiple instances of BPEL trying to access the same message in a High Available Environemnt .....(Singleton BPEL processes) You have to configure the bpel.xml file in your BPEL process to include the following 'clusterGroupId' property name: .....

SomeServicename.wsdl MyClusterName PollingLogicalDeleteService_ptt

This feature uses JGroups underneath for the implementation, hence the clusterGroupId property. These features require cluster and JGroups configuration in

$ORACLE_HOME/bpel/system/config/collaxa-config.xml and $ORACLE_HOME/system/config/jgroups-protocol.xml. All BPEL instances

participating in the cluster must share the same cluster name in collaxa-config.xml,and the same multicast address and port in jgroups-protocol.xml.