bea.com | products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 
Search

WebLogic Server Configuration Reference

 Previous Next Contents Index View as PDF  

JTA

Description

This interface provides access to the JTA configuration attributes. The methods defined herein are applicable for JTA configuration at the domain level.

Syntax

<!ELEMENT JTA EMPTY >
<!ATTLIST JTA
   AbandonTimeoutSeconds      CDATA                    "86400"
   BeforeCompletionIterationLimit
                              CDATA                    "10"
   CheckpointIntervalSeconds  CDATA                    "300"
   ForgetHeuristics           (true | false)           "true"
   MaxTransactions            CDATA                    "10000"
   MaxUniqueNameStatistics    CDATA                    "1000"
   Name                       CDATA                    #REQUIRED
   Notes                      CDATA                    #IMPLIED
   TimeoutSeconds             CDATA                    "30"
>

Parent Elements

The JTA element is a child of the Domain element.

Attributes

Table 44-1 JTAMBean Element Attributes

Attribute

Description

Range of Values and Default

Console Label

Abandon-Timeout-Seconds

The transaction abandon timeout in seconds.

Default: 86400

Minimum: 1

Maximum: java.lang.Integer.MAX_VALUE

Abandon Timeout Seconds

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.

Default: 10

Minimum: 1

Maximum: java.lang.Integer.MAX_VALUE

Before Completion Iteration Limit

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).

Default: 300

Minimum: 10

Maximum: 1800

Checkpoint Interval Seconds

Forget-Heuristics

Returns a boolean indicating whether the transaction manager will automatically perform an XAResource forget operation for transaction heuristic completions.

Default: true

Forget Heuristics

Max-Transactions

The maximum number of simultaneous in-progress transactions allowed on a server.

Default: 10000

Minimum: 1

Maximum: java.lang.Integer.MAX_VALUE

Max Transactions

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")

Default: 1000

Minimum: 0

Maximum: java.lang.Integer.MAX_VALUE

Max Unique Name Statistics

Name

The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.


Name

Notes

Optional information that you can include to describe this configuration.


Notes

Timeout-Seconds

The transaction timeout in seconds.

Default: 30

Minimum: 1

Maximum: java.lang.Integer.MAX_VALUE

Timeout Seconds


 

 

Back to Top Previous Next