Marking transactions as committed

You mark an XA transaction as committed in NexJ System Admin Console after manually committing the transaction in an external system. You mark the transaction to enable the Recovery Manager to attempt to commit the branch.

This functionality is only available for NexJ Server.

To mark a transaction as committed:

1. In NexJ System Admin Console, navigate to the Statistics page.

2. Find and expand the node for your NexJ application, for example, expand nexj.finance. Then, expand the node that contains in-doubt transactions.
   

   

   This functionality is only available for the NexJ application.

3. Select the Recovery Manager node. In-doubt transactions display on top of the details area. Available commands display on the bottom of the details area.
4. In the top of the details area, select the transaction branch that you want to commit. 
   If necessary, use the getAllTransactions command to refresh the list of in-doubt transactions. 
5. In the bottom of the details area, double-click the markCommitted command. The Invoke markCommitted command dialog opens.
6. Double-click in the Value column in the table. The text entry field appears.
7. Enter the transaction ID and branch ID of the branch that you want to mark as committed using the following format: <transaction ID>:<branch ID>
8. Click Invoke. The transaction branch is marked as committed. Operations invoked on a cluster or remote node are output to a log file.
9. If necessary, commit or roll back other branches for the transaction.
10. Click the Close button 

    

     on the top right corner of the dialog. The Invoke markCommitted command dialog closes. The transaction is committed by the Recovery Manager when all in-doubt branches are committed or rolled back for the transaction.

You have marked a transaction branch as committed.

Related tasks

Viewing journal entries of in-doubt XA transactions
Marking transactions as rolled back