Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Domain --> Configuration --> JTA

Tasks Related Topics Attributes

## Overview

On the Domain—>Configuration—>JTA tab in the Administration Console, you can configure Java Transaction API (JTA) attributes to suit your environment. The Administration Console provides default values for all JTA configuration attributes. If you specify an invalid value for any configuration attribute, the WebLogic Server does not boot when you restart it.

Configuration settings for JTA are applicable at the domain level. This means that configuration attribute settings apply to all servers within a domain. Monitoring and logging tasks for JTA are performed at the server level.

Once you configure WebLogic JTA and any transaction participants, the system can perform transactions using the JTA API and the WebLogic JTA extensions.

## Tasks

Configuring JTA

Setting the Transaction Log File Location (Prefix)

Monitoring a Server Instance from the Administration Console

## Related Topics

Programming WebLogic JTA

## Attributes

Table 67-1

Attribute Label | Description | Value Constraints
--- | --- | ---
Timeout Seconds | The transaction timeout in seconds. If the transaction is still in the "active" state after this time (counting from begin()), it is automatically rolled back. Once the transaction moves on to the prepared state, however, this timeout parameter does not apply; the transaction is retried until all the resources are committed. MBean: `weblogic.management. configuration.JTAMBean` Attribute: `TimeoutSeconds` | Minimum: 1 Maximum: 2147483647 Default: 30 Dynamic: yes
Abandon Timeout Seconds | The transaction abandon timeout in seconds. During the second phase of the two-phase commit process, the transaction manager will continue to try to complete the transaction until all resource managers indicate that the transaction is completed. Using the AbandonTimeoutSeconds attribute, you can set the maximum time that a transaction manager will persist in attempting to complete a transaction during the second phase of the transaction. After the abandon transaction timer expires, no further attempt is made to resolve the transaction. If the transaction is in a prepared state before being abandoned, the transaction manager will roll back the transaction to release any locks held on behalf of the abandoned transaction. MBean: `weblogic.management. configuration.JTAMBean` Attribute: `AbandonTimeoutSeconds` | Minimum: 1 Maximum: 2147483647 Default: 86400 Dynamic: yes
Before Completion Iteration Limit | The maximum number of cycles the transaction manager will perform the beforeCompletion synchronization callback. Nothing prevents a Synchronization object from registering another during beforeCompletion, even those whose beforeCompletions have already been called. For example, an EJB can call another in its ejbStore() method. To accomodate this, the transaction manager calls all Synchronization objects, then repeates the cycle if new ones have been registered. This count sets a limit to the number of cycles that can happen. MBean: `weblogic.management. configuration.JTAMBean` Attribute: `BeforeCompletionIterationLimit` | Minimum: 1 Maximum: 2147483647 Default: 10 Dynamic: yes
Max Transactions | The maximum number of simultaneous in-progress transactions allowed on a server. MBean: `weblogic.management. configuration.JTAMBean` Attribute: `MaxTransactions` | Minimum: 1 Maximum: 2147483647 Default: 10000 Dynamic: yes
Max Unique Name Statistics | The maximum number of unique transaction names for which statistics will be maintained. A transaction name typically represents a category of business transactions (such as "funds-transfer") MBean: `weblogic.management. configuration.JTAMBean` Attribute: `MaxUniqueNameStatistics` | Minimum: 0 Maximum: 2147483647 Default: 1000 Dynamic: yes
Checkpoint Interval Seconds | Interval at which the transaction manager creates a new transaction log file and checks all old transaction log files to see if they are ready to be deleted. Default is 300 seconds (5 minutes); minimum is 10 seconds; maximum is 1800 seconds (30 minutes). MBean: `weblogic.management. configuration.JTAMBean` Attribute: `CheckpointIntervalSeconds` | Minimum: 10 Maximum: 1800 Default: 300 Dynamic: yes
Forget Heuristics | Whether or not the transaction manager automatically performs an XA Resource forget() operation for all resources reporting a heuristic decision. The default is true; a forget is issued as soon as the transaction learns of a heuristic outcome. Set it to false only if you know what to do with the resource when it reports a heuristic decision. MBean: `weblogic.management. configuration.JTAMBean` Attribute: `ForgetHeuristics` | Default: true Valid values: true false Dynamic: yes