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" ) MaxTransactions="number MaxUniqueNameStatistics="number Name="String Notes="String TimeoutSeconds="number Type="String
/>
Parent Elements
Attributes
| AbandonTimeoutSeconds | 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. | Admin Console field label: Abandon Timeout SecondsDefault: 86400Minimum: 1Maximum: 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 LimitDefault: 10Minimum: 1Maximum: 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 SecondsDefault: 300Minimum: 10Maximum: 1800 |
| ForgetHeuristics | 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. | Admin Console field label: Forget HeuristicsDefault: true |
| MaxTransactions | The maximum number of simultaneous in-progress transactions allowed on a server. | Admin Console field label: Max TransactionsDefault: 10000Minimum: 1Maximum: 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 StatisticsDefault: 1000Minimum: 0Maximum: 231-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 | 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. | Admin Console field label: Timeout SecondsDefault: 30Minimum: 1Maximum: 231-1 |
| Type | Returns the type of the MBean. | Required: no |
|
|
|