Transaction Timeouts (WebLogic Only)

WebLogic provides a default transaction timeout of 30 seconds, therefore if a transaction is still in an "active" state after this time (counting from begin()), the transaction is automatically rolled back.

Note: Once the transaction moves on to the prepared state, this timeout parameter does not apply; the transaction is retried until all the resources are committed.

Timeouts are useful to prevent a system from locking up if a component is not responding but 30 seconds is usually too short for a production system.

This timeout may not be sufficient for long running transactions in 1Transact, particularly complex transactions such as Refresh WorkspaceA workspace is a virtual environment that one or more users can share to make changes to the data in the database. A workspace logically groups collections of new row versions from one or more version-enabled tables, and isolates these versions until they are explicitly merged with production data or discarded, thus providing maximum concurrency. 1SMS uses workspaces to load in the changes for a job and when validated will merge the changes into the live version of the data, Workspaces are used to check for conflicts to prevent one job from overwriting another job's changes. and Auto Conflict resolution which will be aborted if they take longer than 30 seconds to complete the first phase commit.

It is recommended that you set the 1Transact timeout value to be at least 600 seconds (10 minutes.)

To change this setting, connect to WebLogic Server Administration Console. On the Domain > Configuration > JTA >Timeout Seconds tab, modify the Java Transaction API (JTA) timeout to be a minimum of 600.