Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | JMS Policy Based Client-Side Clustering | Cluster Load Balancing Policies | How Does the Multisend Best Effort Policy Work?
 
How Does the Multisend Best Effort Policy Work?
 
Defining the Maximum Number of Receiving Brokers in a Cluster
In a cluster, if you have defined a multisend best effort policy, the client publishes a message to all, or to the maximum number of Brokers specified in the cluster. For more information about defining the maximum number of receiving Brokers in the cluster, see Defining the Maximum Number of Receiving Brokers in a Cluster.
The publish operation is considered successful if even one of the Brokers receives the message. The message that the client publishes to the Brokers is non-transactional in nature.
Note:
Multisend best effort policy does not work with XA connection factory.
For more information about preventing duplicate message delivery by the webMethods API for JMS to the subscriber, see Message Pre-Acknowledgement.