All Downloads are FREE. Search and download functionalities are using the official Maven repository.

en.help.ref-transactionsvcproperties.html Maven / Gradle / Ivy

There is a newer version: 3.2-b03
Show newest version

Properties Specific to the Transaction Service

The following properties are available for configuring the Transaction Service.

oracle-xa-recovery-workaround

If set to true, the Oracle XA Resource workaround is used in transaction recovery. The default value is true.

disable-distributed-transaction-logging

If set to true, disables transaction logging, which might improve performance. If the On Restart Enabled checkbox is selected, this property is ignored. The default value is false.

xaresource-txn-timeout

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

pending-txn-cleanup-interval

Specifies the interval, in seconds, at which an asynchronous thread checks for pending transactions and completes them. If this property is not specified, there is no default. If this property is present but has no value, the default value is 60.

use-last-agent-optimization

If set to 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. The default value is true.

delegated-recovery

If set to true, cluster-wide delegated recovery is enabled. The default value is false.

wait-time-before-recovery-insec

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

db-logging-resource

Specifies the JNDI name of the JDBC resource for the database to which transactions are logged. For more information, see Chapter 15, Using the Transaction Service, in Oracle GlassFish Server 3.1 Application Development Guide. There is no default value.

xa-servername

Specifies the host name that the transaction service uses to identify transactions being managed by the installed GlassFish Server. This can sometimes be useful for recovering transactions from the log file that was created on a different host running the GlassFish Server.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices




© 2015 - 2024 Weber Informatics LLC | Privacy Policy