oracle-xa-recovery-workaround

true

If true, the Oracle XA Resource workaround is used in transaction recovery.

disable-distributed-transaction-logging

false

If true, disables transaction logging, which might improve performance.

If the automatic-recovery attribute is set to true , this property is ignored.

xaresource-txn-timeout

specific to the XAResource used

Changes the XAResource timeout. In some cases, the XAResource default timeout can cause transactions to be aborted, so it is desirable to change it.

pending-txn-cleanup-interval

none if this property is absent, 60 if this property is present but has no value

Specifies the interval, in seconds, at which an asynchronous thread checks for pending transactions and completes them. 

use-last-agent-optimization

true

If true, enables last agent optimization, which improves the throughput of transactions. If one non-XA resource is used with XA resources in the same transaction, the non XA resource is the last agent.

delegated-recovery

false

If true, cluster-wide delegated recovery is enabled. You must also facilitate storing of transaction logs in a shared file system in one of these ways:

• Set the domain element's log-root attribute to a shared file system base directory and set the tx-log-dir attribute to a relative path.

• Set tx-log-dir to an absolute path to a shared file system directory, in which case log-root is ignored for transaction logs.

• Set a system-property called TX-LOG-DIR to a shared file system directory. For example:

<server config-ref="server-config" name="server">
   <system-property name="TX-LOG-DIR" 
      value="/net/tulsa/nodeagents/na/instance1/logs"/>
</server>

wait-time-before-recovery-insec

60

Specifies the wait time, in seconds, after which an instance starts the recovery for a dead instance. 

db-logging-resource

none 

Specifies the JNDI name of the JDBC resource for the database to which transactions are logged. For more information, see Chapter 16, Using the Transaction Service, in Sun GlassFish Enterprise Server 2.1 Developer’s Guide.

xa-servername

host name on which the Enterprise Server runs 

Specifies the host name that the transaction service uses to identify transactions being managed by the installed Enterprise Server. This can sometimes be useful for recovering transactions from the log file that was created on a different host running the Enterprise Server. This should also be used when the Enterprise Server is installed as part of Sun Cluster HA.