Repository Transaction Timeouts

The 1Integrate Repository is transactional to ensure data consistency, and transaction timeouts are used to abort stuck database updates.

The transaction timeout value can be tuned to your production environment to ensure you don't hit false transaction rollbacks, caused by transactions aborting too soon.

     Note: You must restart your 1Integrate installation for any changes to the transaction timeout to take effect.

WildFly

To change the Repository Timeout in WildFly, enter the following in the settings.properties file, configuring the timeout in seconds:

WebLogic

WebLogic provides a default transaction timeout of 30 seconds. For information on setting the JTA timeout in the WebLogic console, please refer to the relevant Oracle documentation.