BEA Logo BEA Tuxedo Release 7.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy


   Tuxedo Doc Home   |   Administration   |   Topic List   |   Previous   |   Next   |   Contents

   Administering a BEA Tuxedo Application at Run Time

Aborting or Committing Transactions

This topic provides instructions for aborting and committing transactions.

How to Abort a Transaction

To abort a transaction, complete the following procedure.

  1. Enter the following command.

    aborttrans (abort) [-yes] [-g groupname] tranindex

  2. To determine the value of tranindex, run the printtrans command (a tmadmin command).

  3. If groupname is specified, a message is sent to the TMS of that group to mark as "aborted" the transaction for that group. If a group is not specified, a message is sent, instead, to the coordinating TMS, requesting an abort of the transaction. You must send abort messages to all groups in the transaction to control the abort.

This command is useful when the coordinating site is partitioned or when the client terminates before calling a commit or an abort. If the time-out is large, the transaction remains in the transaction table unless it is aborted.

How to Commit a Transaction

To commit a transaction, complete the following procedure.

  1. Enter the following command.

    committrans (commit) [-yes] [-g groupname] tranindex

    Note: Both groupname and tranindex are required arguments.

The operation fails if the transaction is not precommitted or has been marked aborted. This message should be sent to all groups to fully commit the transaction.

Cautions About Using the committrans Command

Be careful about using the committrans command. The only time you need to run it is when both of the following conditions apply:

Also, a client may be blocked on tpcommit(), which will be timed out. If you are going to perform an administrative commit, be sure to inform this client.