The following table describes properties for the transaction-service element.
Table 1–170 transaction-service Properties
Property |
Default |
Description |
---|---|---|
true |
If true, the Oracle XA Resource workaround is used in transaction recovery. |
|
false |
If true, disables transaction logging, which might improve performance. If the automatic-recovery attribute is set to true , this property is ignored. |
|
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. |
|
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. |
|
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. |
|
none |
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 Sun GlassFish Enterprise Server v3 Application Development Guide. |
|
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. |