Skip to main content
Skip table of contents

Viewing journal entries of in-doubt XA transactions

You can view journal entries for XA transactions that are in doubt.

This functionality is only available for NexJ Server.

To view journal entries for XA transactions:

  1. In NexJ System Admin Console, navigate to the Statistics page.
  2. Find and expand the node for your NexJ application, for example, expand 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. For in-doubt transactions, the Count attribute displays the total number of branches in all in-doubt transactions. The Transaction attribute displays the transaction branches that you can mark as committed or rolled back. The following information displays for each transaction branch.
    • xid
      The transaction branch ID. The xid contains the transaction ID followed by the branch ID. A colon (:) separates the transaction and branch ID, for example, xid=2398472398:00 and xid=2398472398:01
    • time
      The last time that any actions were performed on the branch.

    • resource
      The name of the resource that is tracking the branch, for example, an SQL connection.

    • state
      The state of the branch, for example, Committed heuristically.

  4. In the bottom of the details area, double-click the getAllTransactions command. The Invoke getAllTransactions command dialog opens.
  5. Click the Invoke button.
  6. Click the Close button 
     on the top right corner of the dialog. 
    The Invoke getAllTransactions command dialog closes.

You have viewed journal entries for XA transactions that are in doubt.

You can now mark transaction branches as committed or rolled back after you resolve them externally.

Marking transactions as committed
Marking transactions as rolled back

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.