Troubleshooting transactions
Use this overview task to help resolve a problem that you think is related to the Transaction service.
To identify and resolve transaction-related problems, we can use the standard WAS RAS facilities. If we encounter a problem that you think might be related to transactions...
- Check for transaction messages in the admin console.
The Transaction service produces diagnostic messages prefixed by "CWWTR". 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 for more messages in additional places.
Check the appserver's stdout.log.
See about a problem, check the stdout.log file for the appserver, which should contain more error messages and extra details about the problem.
- Check for messages related to the appserver's transaction log directory when the problem occurred.
If we 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, we can copy the transaction logs to the new directory then stop and restart the appserver.
- 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 we have suggestions for other tips, please let the IBM WebSphere writing team know.
Transaction troubleshooting tips
Related tasks
Configuring transaction properties for an appserver
Manage transaction logging for optimum server availability
Use transactions with WebSphere applications