Use this overview task to help resolve a problem that you think
is related to the Transaction service.
About this task
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:
- 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.
- Check for Transaction messages.
Check
the activity log.
Check the error log.
Log messages produced by the Transaction service are
accompanied by Log Analyzer descriptions.
- Check for more messages in additional places.
Check
the application server's stdout.log. For more information about a problem,
check the stdout.log file for the application server, which should contain
more error messages and extra details about the problem.
Check
for more messages in other potential message output repositories. For more
information about a problem, check the standard output file configured by
your administrator. This will contain more error messages and other detailed
information about the problem.
- Check for messages related to the application server'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 application server.
Check the RRS logs for any transaction activity
involving RRS-compliant resources. IBM WebSphere Application Server
for z/OS is capable of supporting both XA and RRS resource managers, and of
coordinating a mix of RRSTransactional resource managers and XA capable resource
managers under the same global transaction. If your installation uses XA resource
managers, RRS resource managers, or a mixture of both, you can use the administrative
console to view transaction logs that contain information about all transactions.
You can find additional information about RRS transactions by using the RRS
panels.
- Check the hints and tips for troubleshooting transactions.
See Transaction troubleshooting tips for
an ongoing collection of troubleshooting tips, based on test and user experience.
If you have suggestions for other tips, please let the IBM WebSphere writing
team know.