The multisend best effort policy specifies that a JMS client send the same JMS message to all, or as many Brokers in the Broker cluster as possible. The publish operation is considered to be successful if even one of the Brokers receives the message. The multisend best effort policy requires the connection to be non-transacted. When sending JMS messages in conjunction with the multisend best effort policy, the connection transaction type must be NO_TRANSACTION. If the connection transaction type is XA_TRANSACTION or LOCAL_TRANSACTION, Integration Server throws a JMSSubsystemException when attempting to enable the connection and the sending service fails.

For information about specifying a transaction type for a JMS connection alias, see webMethods Integration Server Administrator’s Guide.