Troubleshooting transactions

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:

Procedure

  1. Check for transaction messages in the administrative 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.

  2. Check for Transaction messages.

    Check the activity log.

  3. Check for more messages in additional places.

    Check the application server 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.

  4. Check for messages related to the application server 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.
  5. Check the hints and tips for troubleshooting transactions.

    See the topic about 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.

  6. Change the the SCA composite files to use the noManagedTransaction intent. Global and local transactions for SCA are not supported when you use JDBC to connect to resources, so you must use noManagedTransaction intents.
    If you use managed local transaction intent or global transaction intent in SCA composites, this will turn off autocommit when you use JDBC on the IBM i platform. If multiple SQL jobs need to lock the same table for an update, the following exception will appear:
    SQLException: com.ibm.db2.jdbc.app.DB2DBException: Row or object WAREHOUSE in CBIVP type *FILE in use

    The first SQL job that locks the table never commits the transaction, and the lock is never released.

    1. In the SCA composite files, change both managedTransaction.local and managedTransaction.global to noManagedTransaction. Change
      requires="managedTransaction.local"
      and
      requires="managedTransaction.global"
      to
      requires="noManagedTransaction"
    2. In the SCA composite files, change propogateTransaction to suspendsTransaction. Change
      requires="propagatesTransaction"
      to
      requires="suspendsTransaction"



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 7:16:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-iseries&topic=tjta_probd
File name: tjta_probd.html