Transaction Error Situations
When the Integration Server encounters a situation that could compromise transactional integrity, it throws an error. Such situations include the following:
A transaction includes two or more different resources that support only local transactions.
If a transaction accesses multiple resources, and more than one of the resources supports only local transactions, the integrity of the transaction cannot be guaranteed. For example, if the first resource commits successfully, and the second resource fails to commit, the first resource interaction cannot be rolled back; it has been committed already. To help prevent this problem, the Integration Server detects this case when connecting to more than one resource that does not support two-phase commits. It throws a run-time exception and the service execution fails.
Note:
Because this situation may be acceptable in some applications, the adapter user can include an input in the startTransaction service to cause the Integration Server to allow this situation.
A resource is used in both a parent transaction and a nested transaction.
This situation is ambiguous, and most likely means that a nested transaction was not closed properly.
A parent transaction is closed before its nested transaction.
After a service request has invoked all its services, but before returning results to the caller, the service may commit its work. This commit could fail if the resource is unavailable or rejects the commit. This will cause the entire server request to fail and to roll back the transaction.