Transactions might be incomplete either because the server crashed or because a resource manager crashed. 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.
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.
The Transaction Service page opens.
By default, the Enabled checkbox is not selected.
The default value is 600 (10 minutes).
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.
See Also
Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices