Transaction Logging

The transaction service writes transactional activity into transaction logs so that transactions can be recovered. You can control transaction logging in these ways:

Set the location of the transaction log files in one of these ways:
- Set the GlassFish Server's log-root setting to a shared file system base directory and set the transaction service's 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:
```
asadmin> create-system-properties --target server TX-LOG-DIR=/inst1/logs
```
For information about setting log-root and other general logging settings, see Chapter 7, Administering the Logging Service.
Turn off transaction logging by setting the disable-distributed-transaction-logging property to true and the automatic-recovery attribute to false. Do this only if performance is more important than transaction recovery.

Note - All instances in a cluster must be owned by the same user (uid), and read/write permissions for that user must be set on the transaction log directories.

Transaction logs should be stored in a high-availability network file system (NFS) to avoid a single point of failure.

To Store Transaction Logs in a Database

For multi-core machines, logging transactions to a database may be more efficient.

This feature is intended for resource recovery on a standalone server instance while the instance is healthy, not for a server crash. It is not intended for use on a cluster.

Create a JDBC connection Pool, and set the non-transactional-connections attribute to true.
Create a JDBC resource that uses the connection pool and note the JNDI name of the JDBC resource.
Create a table named txn_log_table with the following schema:

Column Name

JDBC Type

LOCALTID

BIGINT

SERVERNAME

VARCHAR(n)

GTRID

VARBINARY

The size of the SERVERNAME column should be at least the length of the GlassFish Server host name plus 10 characters.
The size of the GTRID column should be at least 64 bytes.
Add the db-logging-resource property to the transaction service. For example:
```
asadmin set server-config.transaction-service.property.db-logging-resource="jdbc/TxnDS"
```
The property's value should be the JNDI name of the JDBC resource configured previously.
To disable file synchronization, use the following asadmin create-jvm-options command:
```
asadmin create-jvm-options -Dcom.sun.appserv.transaction.nofdsync
```
Restart the server.

Next Steps

To define the SQL used by the transaction manager when it is storing its transaction logs in the database, use the following flags:

-Dcom.sun.jts.dblogging.insertquery=sql statement

-Dcom.sun.jts.dblogging.deletequery=sql statement

The default statements are as follows:

-Dcom.sun.jts.dblogging.insertquery=insert into txn_log_table values ( ?, ?, ? )

-Dcom.sun.jts.dblogging.deletequery=delete from txn_log_table where localtid = ? and servername = ?

To set one of these flags using the asadmin create-jvm-options command, you must quote the statement. For example:

create-jvm-options '-Dcom.sun.jts.dblogging.deletequery=delete from txn_log_table where gtrid = ?'

You can also set JVM options in the Administration Console. Select the JVM Settings component under the relevant configuration. These flags and their statements must also be quoted in the Administration Console. For example:

'-Dcom.sun.jts.dblogging.deletequery=delete from txn_log_table where gtrid = ?'

Skip Navigation Links
Exit Print View
	Oracle GlassFish Server 3.1 Administration Guide