Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# Transaction Failures and Rollbacks

In the transaction example in A Local Transaction, all the external data updates and iProcess case data updates are saved to memory until the case has been processed. Once the processing completes, all the updates are written to the database. This is known as the Commit process.

However, if one or more steps in the transaction are not possible (such as the unavailability of the database), none of the updates are committed and the data is left in the same state as when the transaction started. This is known as the rollback process. Similarly, if the connection to the database is broken, any outstanding transactions are rolled back.

If the instruction is received by the Background but one of the steps it processes subsequently fails (such as a COM+ EAI step calling an application that is not running), then the resource manager returns an error to the Mbox daemon. The Mbox daemon aborts the transaction while the resource manager ensures that all of the steps involved in the transaction are rolled back to their initial state.

Subtopics

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.