Transactions might be incomplete either because the server crashed or a resource manager crashed. It is essential to complete these stranded transactions and recover from the failures. Enterprise Server is designed to recover from these failures and complete the transactions upon server startup.
While performing the recovery, if some of the resources are unreachable the server restart may be delayed as it tries to recover the transactions.
When the transaction spans across servers, the server that started the transaction can contact the other servers to get the outcome of the transactions. If the other servers are unreachable, the transaction uses the Heuristic Decision field to determine the outcome.
In the tree component select the Configurations node.
If you are running a non-clustered domain in developer profile, skip to the next step. If you are running the domain in cluster profile, select the instance to configure:
Select the Transaction Service node.
To enable the recovery of incomplete transactions, check the Recover in the On Restart field.
Set the amount of time, in seconds, the Enterprise Server tries to connect to the unreachable server in the Retry Timeout field. The default value is 10 minutes (600 seconds).
Set the policy for unreachable servers in a transaction in the Heuristic Decision field.
Unless there is a good reason to set this field to Commit, leave Heuristic Decision set to Rollback. Committing indeterminate transactions can compromise the data integrity of your application.
Set any needed properties.
Click the Add Properties button, type values in the Name and Value fields, and check the box to the left of the Name to activate the property.
Restart the Enterprise Server.