Domains: Configuration: JTA

edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Domains: Configuration: JTA

Domains: Configuration: JTA

Configuration Options Advanced Configuration Options Related Tasks Related Topics
Use this page to define the Java Transaction API (JTA) configuration of this WebLogic Server domain.
Configuration Options

Name Description

Timeout Seconds
The transaction timeout seconds for active transactions, before the prepared state.
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 does not apply; the transaction is retried until all the resources are committed.
MBean Attribute: JTAMBean.TimeoutSeconds
Minimum value: 1
Maximum value: 2147483647
Abandon Timeout Seconds
The transaction abandon timeout seconds for transactions in the second phase of the two-phase commit (prepared and later).
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 this timeout, 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 Attribute:
JTAMBean.AbandonTimeoutSeconds
Minimum value: 1
Maximum value: 2147483647
Before Completion Iteration Limit
The maximum number of cycles that the transaction manager will perform the beforeCompletion synchronization callback for this WebLogic Server domain.
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 accommodate this, the transaction manager calls all Synchronization objects, then repeats the cycle if new ones have been registered. This count sets a limit to the number of cycles that can happen.
MBean Attribute: JTAMBean.BeforeCompletionIterationLimit
Minimum value: 1
Maximum value: 2147483647
Max Transactions
The maximum number of simultaneous in-progress transactions allowed on a server in this WebLogic Server domain.
MBean Attribute:
JTAMBean.MaxTransactions
Minimum value: 1
Maximum value: 2147483647
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 Attribute:
JTAMBean.MaxUniqueNameStatistics
Minimum value: 0
Maximum value: 2147483647
Checkpoint Interval Seconds
The 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.
MBean Attribute:
JTAMBean.CheckpointIntervalSeconds
Minimum value: 10
Maximum value: 1800
Forget Heuristics
Whether the transaction manager will automatically perform an XA Resource forget operation for heuristic transaction completions.
When enabled, the transaction manager automatically performs an XA Resource forget() operation for all resources as soon as the transaction learns of a heuristic outcome. Disable this feature only if you know what to do with the resource when it reports a heuristic decision.
MBean Attribute: JTAMBean.ForgetHeuristics
Unregister Resource Grace Period
The grace period (number of seconds) that the transaction manager waits for transactions involving the resource to complete before unregistering a resource. The grace period can help minimize the risk of abandoned transactions because of an unregistered resource, such as a JDBC data source module packaged with an application.
During the specified grace period, the unregisterResource call will block until the call can return, and no new transactions are started for the associated resource. If the number of outstanding transactions for the resource goes to 0, the unregisterResource call returns immediately.
At the end of the grace period, if there are still outstanding transactions associated with the resource, the unregisterResource call returns and a log message is written on the server on which the resource was previously registered.
MBean Attribute: JTAMBean.UnregisterResourceGracePeriod
Minimum value: 0
Maximum value: 2147483647

Advanced Configuration Options

Name Description

Security Interoperability Mode
Specifies the security mode of the communication channel used for XA calls between servers that participate in a global transaction. All server instances in a domain must have the same security mode setting.
Security Interoperability Mode options:

default
The transaction coordinator makes calls using the kernel identity over an admin channel if it is enabled, and anonymous otherwise. Man-in-the-middle attacks are possible if the admin channel is not enabled.
performance The transaction coordinator makes calls using anonymous at all times. This implies a security risk since a malicious third party could then try to affect the outcome of transactions using a man-in-the-middle attack.
compatibility The transaction coordinator makes calls as the kernel identity over an insecure channel. This is a high security risk because a successful man-in-the-middle attack would allow the attacker to gain administrative control over both domains. This setting should only be used when strong network security is in place.
MBean Attribute: JTAMBean.SecurityInteropMode Changes take effect after you redeploy the module or restart the server.
Maximum Duration of XA Calls
Maximum allowed duration of XA calls to resources. If a particular XA call to a resource exceeds the limit, the resource is declared unavailable.
MBean Attribute:
JTAMBean.MaxXACallMillis
Minimum value: 0
Maximum value: 9223372036854775807
Maximum Duration XA Resource Unavailable
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.
MBean Attribute:
JTAMBean.MaxResourceUnavailableMillis
Minimum value: 0
Maximum value: 9223372036854775807
Maximum Resource Requests on a Server
Maximum number of concurrent requests to resources allowed for each server.
MBean Attribute:
JTAMBean.MaxResourceRequestsOnServer
Minimum value: 10
Maximum value: 2147483647

Related Tasks

Configure domain JTA options
Configure JTA

Related Topics

Programming WebLogic JTA

Name	Description
Timeout Seconds	The transaction timeout seconds for active transactions, before the prepared state. 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 does not apply; the transaction is retried until all the resources are committed.` `MBean Attribute: JTAMBean.TimeoutSeconds` `Minimum value: 1` `Maximum value: 2147483647`
Abandon Timeout Seconds	The transaction abandon timeout seconds for transactions in the second phase of the two-phase commit (prepared and later). 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 this timeout, 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 Attribute: `JTAMBean.AbandonTimeoutSeconds` `Minimum value: 1` `Maximum value: 2147483647`
Before Completion Iteration Limit	The maximum number of cycles that the transaction manager will perform the `beforeCompletion` synchronization callback for this WebLogic Server domain. 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 accommodate this, the transaction manager calls all Synchronization objects, then repeats the cycle if new ones have been registered. This count sets a limit to the number of cycles that can happen.` `MBean Attribute: JTAMBean.BeforeCompletionIterationLimit` `Minimum value: 1` `Maximum value: 2147483647`
Max Transactions	The maximum number of simultaneous in-progress transactions allowed on a server in this WebLogic Server domain. MBean Attribute: `JTAMBean.MaxTransactions` `Minimum value: 1` `Maximum value: 2147483647`
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 Attribute: `JTAMBean.MaxUniqueNameStatistics` `Minimum value: 0` `Maximum value: 2147483647`
Checkpoint Interval Seconds	The 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. MBean Attribute: `JTAMBean.CheckpointIntervalSeconds` `Minimum value: 10` `Maximum value: 1800`
Forget Heuristics	Whether the transaction manager will automatically perform an XA Resource `forget operation for heuristic transaction completions.` `When enabled, the transaction manager automatically performs an XA Resource forget() operation for all resources as soon as the transaction learns of a heuristic outcome. Disable this feature only if you know what to do with the resource when it reports a heuristic decision.` `MBean Attribute: JTAMBean.ForgetHeuristics`
Unregister Resource Grace Period	The grace period (number of seconds) that the transaction manager waits for transactions involving the resource to complete before unregistering a resource. The grace period can help minimize the risk of abandoned transactions because of an unregistered resource, such as a JDBC data source module packaged with an application. During the specified grace period, the unregisterResource call will block until the call can return, and no new transactions are started for the associated resource. If the number of outstanding transactions for the resource goes to `0, the unregisterResource call returns immediately.` `At the end of the grace period, if there are still outstanding transactions associated with the resource, the unregisterResource call returns and a log message is written on the server on which the resource was previously registered.` `MBean Attribute: JTAMBean.UnregisterResourceGracePeriod` `Minimum value: 0` `Maximum value: 2147483647`

Name	Description
Security Interoperability Mode	Specifies the security mode of the communication channel used for XA calls between servers that participate in a global transaction. All server instances in a domain must have the same security mode setting. Security Interoperability Mode options: default The transaction coordinator makes calls using the kernel identity over an admin channel if it is enabled, and `anonymous otherwise. Man-in-the-middle attacks are possible if the admin channel is not enabled.` `performance The transaction coordinator makes calls using anonymous at all times. This implies a security risk since a malicious third party could then try to affect the outcome of transactions using a man-in-the-middle attack.` `compatibility The transaction coordinator makes calls as the kernel identity over an insecure channel. This is a high security risk because a successful man-in-the-middle attack would allow the attacker to gain administrative control over both domains. This setting should only be used when strong network security is in place.` `MBean Attribute: JTAMBean.SecurityInteropMode Changes take effect after you redeploy the module or restart the server.`
Maximum Duration of XA Calls	Maximum allowed duration of XA calls to resources. If a particular XA call to a resource exceeds the limit, the resource is declared unavailable. MBean Attribute: `JTAMBean.MaxXACallMillis` `Minimum value: 0` `Maximum value: 9223372036854775807`
Maximum Duration XA Resource Unavailable	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. MBean Attribute: `JTAMBean.MaxResourceUnavailableMillis` `Minimum value: 0` `Maximum value: 9223372036854775807`
Maximum Resource Requests on a Server	Maximum number of concurrent requests to resources allowed for each server. MBean Attribute: `JTAMBean.MaxResourceRequestsOnServer` `Minimum value: 10` `Maximum value: 2147483647`