IBM Support

TroubleShooting: Java Transaction Service (JTS) problems

Technote (troubleshooting)


Problem(Abstract)

Troubleshooting for Java Transaction Service (JTS) problems in IBM WebSphere Application Server. This should help address common issues with this component before calling IBM support and save you time.

Resolving the problem

Tab navigation


It is a good start to refer to the following Knowledge Center links while troubleshooting Transaction issues in WebSphere Application Server:

Troubleshooting transactions

Transaction troubleshooting tips

Transaction service exceptions

Recovering from failed transaction recovery

The below two WebSphere Support Technical Exchanges provides an overview of the Java Transaction Service in WebSphere Application Server and shows how to resolve common problems such as transaction time-outs, rollbacks, and recovery issues:

Transactions in WebSphere Application Server - Overview and Problem Determination

Understanding Transaction Manager in WebSphere Application Server


Steps to help resolve JTS problems
  1. Does the following message appear in the SystemOut.log file?


    WTRN0006W: Transaction {0} has timed out after {1} seconds.
  2. Does the following error message appear in the SystemOut.log file?


    WTRN0062E: An illegal attempt to use multiple resources that have only one-phase capability has occurred within a global transaction.
    • Yes, review the documents found here. This error indicates that more than one non-XA resources were enlisted in a global transaction (either a UserTransaction or a Container-managed transaction). You should ensure that all resources (for example: Data sources and connection factories) that are enlisted in the transaction are XA-enabled.
    • No, continue to question 3.

  3. Does the following error message appear in the SystemOut.log file?


    WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.
    • Yes, review the documents found here. You should ensure that all resources (for example: Data sources and connection factories) that are enlisted in the transaction are XA-enabled.
    • No, continue to question 4.

  4. Does the following message appear in the SystemOut.log file when starting the application server?


    WTRN0037W:  The transaction service encountered an error on an xa_recover operation. The resource was {0}. The error code was {1}. The exception stack trace follows: {2}
    • Yes, review the documents found here. This error indicates that an application server was brought down uncleanly, perhaps because of a crash or power outage. When the application server starts again, it will try to recover any unresolved transactions. The error means that there was a failure during transaction recovery. If you do not need to recover the transactions, you can avoid the problem by deleting the transaction logs in the following directory:

      install_root/profiles/profile_name/tranlog
    • No, continue to question 5.


  5. Is the problem related to an XAException occurring?

    • Yes, review the documents found here.
    • No, continue to question 6.
  6. Is the problem occurring on system running WebSphere Process Server?
What to do next
If the preceding troubleshooting steps did not solve your problem, see the MustGather for JTS problems to continue investigation.

NOTE: It is NOT recommended to simply delete the transaction logs in order to definitively resolve a transaction-related issue. Proper debugging steps, including enabling a transaction service trace should be followed to determine the root cause.


Cross reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK

Document information

More support for: WebSphere Application Server
Java Transaction Service (JTS)

Software version: 7.0, 8.0, 8.5, 8.5.5, 9.0

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: Base, Enterprise, Express, Network Deployment, WebSphere Business Integrations Server Foundation

Reference #: 1247192

Modified date: 22 August 2013