Resource recovery is a configurable option that provides object persistence and recovery operations. Basic persistence is achieved by writing transactions to a transaction log that contains all the information necessary to re-create the transaction. Persistence is supported for the CosTransactions::Resource and CosTransactions::Synchronization objects that are registered with the transaction. Recovery is supported for JDBC connectors and native type resources that are registered with EAServer. When EAServer starts, the recovery manager is called, which reads the transaction log and starts transaction recovery.
Recovery
operations can be performed only for transaction logs that were
created for EAServer version 5.0 or later.
A transaction log provides enhanced debugging and integrates with the standard EAServer logging functionality. Monitoring functionality is also provided, which allows you to use the Management Console to view statistics, such as the total number of committed transactions and the average duration of transactions.
When EAServer starts, the TransactionLogManager verifies the transaction log’s integrity, automatically does necessary repairs, then runs the transaction log defragmenter. This helps to allocate space for new transactions. The recovery manager passes transaction information to the TransactionLogManager, which is responsible for storing and deleting the transaction record from the transaction log.
You can set the following recovery options on the Transactions tab of the Server Properties dialog box:
Enable Recovery – check to enable.
Recovery Log File Name – enter the name of the file in which to store the transaction log. You can specify a file name only, or an absolute path to a file. If you specify a file name only, the file is created in the logs subdirectory or your EAServe installation.
Log File Size – enter the maximum file size.
