en.help.task-configtransrecovery.html Maven / Gradle / Ivy
To Configure How the GlassFish Server Recovers Transactions
Transactions might be incomplete either because the server crashed or because a resource manager crashed between phases of a 2-phase commit. It is essential to complete these stranded transactions and recover from the failures. GlassFish Server is designed to recover from these failures and complete the transactions upon server startup.
Before performing the recovery, make sure all the resources involved are up and running.
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 navigation tree, expand the Configuration node.
-
Select the instance to configure:
-
To configure a particular instance, select the instance's config node. For example, the default instance, server
, select the server-config
node.
-
To configure the default settings for all instances, select the default-config
node.
-
Select the Transaction Service node.
The Transaction Service page opens.
-
On the Transaction Service page, select the On Restart Enabled checkbox to enable the recovery of incomplete transactions.
By default, the Enabled checkbox is not selected.
-
In the Retry Timeout field, type the number of seconds the GlassFish Server tries to connect to an unreachable server.
The default value is 600 (10 minutes).
-
From the Heuristic Decision drop-down list, select the policy for unreachable servers in a transaction.
Unless there is a good reason to select Commit, leave Heuristic Decision set to Rollback (the default). Committing indeterminate transactions can compromise the data integrity of your application.
-
Click Save.
-
Restart the GlassFish Server.
See Also
-
-
-
-
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices