Error Handling for Transaction Type of XA_TRANSACTION or LOCAL_TRANSACTION
When sending JMS messages using a multisend guaranteed policy with a connection of type of XA_TRANSACTION or LOCAL_TRANSACTION, the following error handling may occur:
If the minimum number of
Brokers required by the multisend guaranteed policy are not available and the transaction type is XA_TRANSACTION or LOCAL_TRANSACTION,
Integration Server throws an ISRuntimeException and the service fails.
Integration Server considers this a transient error. Consequently, you can configure service retry to instruct
Integration Server to retry the top-level service automatically.
If a fatal error occurs while
Integration Server is sending messages to multiple
Brokers,
Integration Server throws a ServiceException and the sending service fails. For example, an invalid destination lookup name or invalid connection factory name results in a ServiceException and thus a fatal error.
Integration Server rolls back the transaction after a fatal error.
If a transient error occurs while
Integration Server is sending messages to multiple
Brokers and the connection transaction type is XA_TRANSACTION or LOCAL_TRANSACTION,
Integration Server throws an ISRuntimeException and rolls back the transaction.
You can configure a service to re-execute automatically after an ISRuntimeException occurs. For more information about configuring service retry, see webMethods Service Development Help.