bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

WebLogic Server Configuration Reference

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

>     <JTA
>       AbandonTimeoutSeconds="number"
>       BeforeCompletionIterationLimit="number"
>       CheckpointIntervalSeconds="number"
>       ForgetHeuristics=( "true" | "false" )
>       MaxResourceRequestsOnServer="number"
>       MaxResourceUnavailableMillis="number"
>       MaxTransactions="number"
>       MaxUniqueNameStatistics="number"
>       MaxXACallMillis="number"
>       Name="String"
>       Notes="String"
>       TimeoutSeconds="number"
>     />

Parent Elements

- Domain

- Server

Attributes

Table 37-1 JTA attributes

Attribute | Description | Range of Values and Default
--- | --- | ---
AbandonTimeoutSeconds | Returns the transaction abandon timeout in seconds. | Admin Console field label: Abandon Timeout Seconds Required: no Default: 86400 Minimum: 1 Maximum: 231-1
BeforeCompletionIterationLimit | 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. | Admin Console field label: Before Completion Iteration Limit Required: no Default: 10 Minimum: 1 Maximum: 231-1
CheckpointIntervalSeconds | 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). | Admin Console field label: Checkpoint Interval Seconds Required: no Default: 300 Minimum: 10 Maximum: 1800
ForgetHeuristics | Returns a boolean indicating whether the transaction manager will automatically perform an XAResource forget operation for transaction heuristic completions. | Admin Console field label: Forget Heuristics Required: no Default: true
MaxResourceRequestsOnServer | Maximum number of concurrent requests to resources allowed for each server. | Required: no Default: 50 Minimum: 10 Maximum: 231-1
MaxResourceUnavailableMillis | Maximum duration in milliseconds that a resource is declared dead. After the duration, the resource will be declared available again, even if the resource provider does not explicitly re-register the resource. | Required: no Default: 1800000 Minimum: 0 Maximum: 263-1
MaxTransactions | The maximum number of simultaneous in-progress transactions allowed on a server. | Admin Console field label: Max Transactions Required: no Default: 10000 Minimum: 1 Maximum: 231-1
MaxUniqueNameStatistics | 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") | Admin Console field label: Max Unique Name Statistics Required: no Default: 1000 Minimum: 0 Maximum: 231-1
MaxXACallMillis | Maximum allowed duration of XA calls to resources. If a particular XA call to a resource exceeds the limit, the resource is declared unavailable. | Required: no Default: 120000 Minimum: 0 Maximum: 263-1
Name | The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. | Required: no
Notes | Optional information that you can include to describe this configuration. | Required: no
TimeoutSeconds | Returns the transaction timeout in seconds. | Admin Console field label: Timeout Seconds Required: no Default: 30 Minimum: 1 Maximum: 231-1