bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Domain --> Configuration --> JTA

Tasks Additional Documentation 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

Monitoring Transactions

Specifying the Transaction Log File Location (Prefix)

Additional Documentation

(Requires an Internet connection.)

"Managing Transactions" in the WebLogic Server Administration Guide

Programming WebLogic JTA

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Timeout Seconds | The transaction timeout in seconds. MBean: weblogic.management. configuration.JTAMBean Attribute: TimeoutSeconds | Minimum: 1 Maximum: java.lang.Integer.MAX_VALUE Default: 30 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Abandon Timeout Seconds | The transaction abandon timeout in seconds. MBean: weblogic.management. configuration.JTAMBean Attribute: AbandonTimeoutSeconds | Minimum: 1 Maximum: java.lang.Integer.MAX_VALUE Default: 86400 Configurable: yes Dynamic: yes Readable: yes Writable: 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: java.lang.Integer.MAX_VALUE Default: 10 Configurable: yes Dynamic: yes Readable: yes Writable: 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: java.lang.Integer.MAX_VALUE Default: 10000 Configurable: yes Dynamic: yes Readable: yes Writable: 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: java.lang.Integer.MAX_VALUE Default: 1000 Configurable: yes Dynamic: yes Readable: yes Writable: 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 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Forget Heuristics | Returns a boolean indicating whether the transaction manager will automatically perform an XAResource forget operation for transaction heuristic completions. MBean: weblogic.management. configuration.JTAMBean Attribute: ForgetHeuristics | Default: true Configurable: yes Dynamic: yes Readable: yes Writable: yes