The transaction manager controls the boundaries of the transaction and is responsible for the final decision as to whether or not the total transaction should commit or rollback. This decision is made in two phases, called the Two-Phase Commit Protocol.
In the first phase, the transaction manager polls all of the resource managers (RDBMSs) involved in the distributed transaction to see if each one is ready to commit. If a resource manager cannot commit, it responds negatively and rolls back its particular part of the transaction so that data is not altered.
In the second phase, the transaction manager determines if any of the resource managers have responded negatively, and, if so, rolls back the whole transaction. If there are no negative responses, the translation manager commits the whole transaction, and returns the results to the application.
samedi 27 octobre 2007
Inscription à :
Publier les commentaires (Atom)
Archives du blog
-
▼
2007
(20)
-
▼
octobre
(20)
- Degrees of isolation (degrees of Consistency)
- Serializability
- Concurrent Transactions
- Isolation and ACID properties
- Java Transaction Design Strategies
- UserTransaction Interface
- TransactionManager Interface
- Oracle SQL Transaction Management
- XAResource interface
- JTA Interfaces
- Two-Phase Commit Protocol
- Transaction Branch
- XA Specification
- Transaction Manager
- The Application Server
- The Resource Adapter
- The Resource Manager
- Distributed Transaction Processing Model
- Distributed Transaction
- JTA
-
▼
octobre
(20)
Aucun commentaire:
Enregistrer un commentaire