[V5.1 and later]Troubleshooting transactions

Use this overview task to help resolve a problem that you think is related to the Transaction service.

 

Overview

To identify and resolve transaction-related problems, you can use the standard WebSphere Application Server RAS facilities. If you encounter a problem that you think might be related to transactions, complete the following steps:

  1. Check for transaction messages in the administrative console. The Transaction service produces diagnostic messages prefixed by "WTRN". The error message indicates the nature of the problem and provides some detail. The associated message information provides an explanation and any user actions to resolve the problem.

  2. Check for Transaction messages in the log.Log messages produced by the Transaction service are accompanied by Log Analyzer descriptions.

  3. Check for more messages in the appserver's stdout.log.For more information about a problem, check the stdout.log file for the appserver, which should contain more error messages and extra details about the problem.

  4. Check for messages related to the appserver's transaction log directory when the problem occurred.

    Note: If you changed the transaction log directory and a problem caused the application server to fail (with in-flight transactions) before the server was restarted properly, the server will next start with the new log directory and be unable to automatically resolve in-flight transactions that were recorded in the old log directory. To resolve this, you can copy the transaction logs to the new directory then stop and restart the appserver.

Related tasks
Configuring transaction properties for an appserver
Managing transaction logging for optimum server availability
Using the transaction service