Troubleshooting: Timeouts occur during a server start and store publish

When starting your WebSphere Commerce server or publishing a store, you might encounter a transaction timeout.

Problem

Transaction timeout errors occur when you are attempting to start the server, or publish a store. For example, the following errors are in the SystemOut.log:
TimeoutManage I   WTRN0006W: Transaction
000001099357C2970000000100000004ECFED
88BFED69AEE8FD3D1CC3B1A5DC7EEBFC910000001099357C2970000000100000004ECFED88BFED6
9AEE8FD3D1CC3B1A5DC7EEBFC91000000001 has timed out after 1200
seconds.

Solution

This error is caused because the Total Transaction Lifetime Timeout variable is not set to a large enough value. Depending on the size of the store, and your hardware configuration, the default value of 1200 seconds might not be sufficient. To increase the Total Transaction Lifetime Timeout, complete the following steps:

  1. Log in to the WebSphere Application Server administrative console.
  2. For each affected WebSphere Application Server running the WebSphere Commerce application, do the following steps:
    1. Go to Servers > Application Servers > instance_name > Container Services > Transaction Service.
    2. Expand the Container Services section, then select Transaction Service.
    3. Update the value of the Total Transaction Lifetime Timeout variable.
    4. Click OK.
  3. Save your changes, and log out of the WebSphere Application Server administrative console.

For more information, see the Transaction service settings.

For general information about the WTRN0006W timeout error, see the Demystifying WTRN0006W article on IBM developerWorks.