TroubleShooting: Java Transaction Service (JTS) problems for V5.0, V5.1, and V6.0
 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

1. Learning more 2. Troubleshooting 3. Collecting data

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:
      • For releases of V5.0 and V5.1:

        install_root/tranlog

      • For releases of V6.0:

        install_root/profiles/profile_name/tranlog

    • No, continue to question 5.

  5. Does the application use message-driven beans (MDBs)?
    • Yes, continue to question 6.

    • No, continue to question 7.

  6. Is the problem related to messages being processed out of order after a transaction rollback?
    • Yes, review this technote.

    • No, continue to question 7.

  7. Is the problem related to an XAException occurring?
    • Yes, review the documents found here.

    • No, continue to question 8.

  8. Review the WebSphere Application Server V5.0, V5.1, or V6.0 Information Center, or the WebSphere Application Server support site for additional information that might help you to resolve the problem.

What to do next
If the preceding troubleshooting steps did not solve your problem, see the MustGather for JTS problems to continue investigation.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Transaction Service (JTS)
Operating system(s): Windows
Software version: 6.0.2
Software edition:
Reference #: 1247192
IBM Group: Software Group
Modified date: Sep 17, 2007