WebSphere automatically rolls back transactions that don’t complete in a certain number of seconds. The default setting is 120 seconds, which may be too short for compiling certain complex pages, especially pages that embed many page fragments.
When you are developing an application, a page must be recompiled each time you change it. If your application includes complex pages (particularly if you are developing a portal with ATG Portal), you can avoid transaction timeouts by raising the timeout setting to 600 seconds. Before deploying the application on a production site, you should precompile all of the pages. You can then lower the timeout setting.
Note also that if the timeout setting is too low, you may experience problems with full Content Administration deployments.
To set the transaction timeout:
In the WebSphere Integrated Solutions Console, expand Servers, then click Application Servers.
Click the link for the server you want to edit.
Under Container Settings, expand Container Services.
Click Transaction Service.
Change the Total transaction lifetime timeout to a large value, for example, 500000.
Change the Maximum transaction timeout to a large value, for example, 500000.
Click OK.
Click Save to save your changes to the master configuration.
