| |
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 Specifies the maximum amount of time, in seconds, an active transaction is allowed to be in the first phase of a two-phase commit transaction. If the specified amount of time expires, the transaction is automatically rolled back.
MBean Attribute:
JTAMBean.TimeoutSecondsMinimum value:
1Maximum value:
2147483647Abandon Timeout Seconds Specifies the maximum amount of time, in seconds, a transaction manager persists in attempting to complete the second phase of a two-phase commit transaction.
During the second phase of a two-phase commit transaction, the transaction manager continues to try to complete the transaction until all resource managers indicate that the transaction is completed. 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 rolls back the transaction to release any locks held on behalf of the abandoned transaction.
MBean Attribute:
JTAMBean.AbandonTimeoutSecondsMinimum value:
1Maximum value:
2147483647Before Completion Iteration Limit The maximum number of cycles that the transaction manager performs the beforeCompletion synchronization callback for this WebLogic Server domain.
Nothing prevents a Synchronization object from registering another during
beforeCompletion, even those whosebeforeCompletionshave already been called. For example, an EJB can call another in itsejbStore()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 synchronization occurs.MBean Attribute:
JTAMBean.BeforeCompletionIterationLimitMinimum value:
1Maximum value:
2147483647Max Transactions The maximum number of simultaneous in-progress transactions allowed on a server in this WebLogic Server domain.
MBean Attribute:
JTAMBean.MaxTransactionsMinimum value:
1Maximum value:
2147483647Max Unique Name Statistics The maximum number of unique transaction names for which statistics are maintained.
The first 1001 unique transaction names are maintained as their own transaction name and stored in each statistic. After the 1001st transaction name is reached, the transaction name is stored as
weblogic.transaction.statistics.namedOverflow, and the transaction statistic is also merged and maintained inweblogic.transaction.statistics.namedOverflow.A transaction name typically represents a category of business transactions, such as "funds-transfer."
MBean Attribute:
JTAMBean.MaxUniqueNameStatisticsMinimum value:
0Maximum value:
2147483647Checkpoint 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.CheckpointIntervalSecondsMinimum value:
10Maximum value:
1800Forget Heuristics Specifies whether the transaction manager automatically performs an XA Resource
forgetoperation 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.ForgetHeuristicsUnregister Resource Grace Period The amount of time, in seconds, a transaction manager waits for transactions involving the resource to complete before unregistering a resource. This grace period helps 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
unregisterResourcecall blocks until the call returns and no new transactions are started for the associated resource. If the number of outstanding transactions for the resource goes to0, theunregisterResourcecall returns immediately.At the end of the grace period, if outstanding transactions are associated with the resource, the
unregisterResourcecall returns and a log message is written to the server on which the resource was previously registered.MBean Attribute:
JTAMBean.UnregisterResourceGracePeriodMinimum value:
0Maximum value:
2147483647Execute XA Calls In Parallel Indicates that XA calls are executed in parallel if there are available threads.
MBean Attribute:
JTAMBean.ParallelXAEnabledEnable Two Phase Commit Indicates that the two-phase commit protocol is used to coordinate transactions across two or more resource managers.
If not selected:
Two-phase commit is disabled and any attempt to use two-phase commit results in a RollbackException being thrown.
All transaction logging is disabled, including checkpoint records.
MBean Attribute:
JTAMBean.TwoPhaseEnabledChanges take effect after you redeploy the module or restart the server.
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
anonymousotherwise. Man-in-the-middle attacks are possible if the admin channel is not enabled.- performance
The transaction coordinator makes calls using
anonymousat 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.SecurityInteropModeChanges take effect after you redeploy the module or restart the server.
Maximum Duration of XA Calls Maximum allowed time duration, in milliseconds, for XA calls to resources. If a particular XA call to a resource exceeds the limit, the resource is declared unavailable.
MBean Attribute:
JTAMBean.MaxXACallMillisMinimum value:
0Maximum value:
9223372036854775807Maximum Duration XA Resource Unavailable Maximum duration time, in milliseconds, that a resource is declared dead. After the duration, the resource is declared available again, even if the resource provider does not explicitly re-register the resource.
MBean Attribute:
JTAMBean.MaxResourceUnavailableMillisMinimum value:
0Maximum value:
9223372036854775807Maximum Resource Requests on a Server Maximum number of concurrent requests to resources allowed for each server.
MBean Attribute:
JTAMBean.MaxResourceRequestsOnServerMinimum value:
10Maximum value:
2147483647Web Service Transactions Transport Security Mode Specifies transport security mode required by WebService Transaction endpoints.
Transport Security options:
- SSLNotRequired
All WebService Transaction protocol messages are exchanged over the HTTP channel.
- SSLRequired
All WebService Transaction protocol messages are and can only be exchanged over the HTTPS.
- ClientCertRequired
All WebService Transaction protocol messages are and can only be exchanged over the HTTPS, and WLS enforces the presence of client certificate
MBean Attribute:
JTAMBean.WSATTransportSecurityModeChanges take effect after you redeploy the module or restart the server.
Web Service Transactions Issued Token Enabled Specifies whether to use
issuedtokento enable authentication between the WS-AT coordinator and participant.MBean Attribute:
JTAMBean.WSATIssuedTokenEnabledChanges take effect after you redeploy the module or restart the server.
Completion Timeout Specifies the maximum amount of time, in seconds, a transaction manager waits for all resource managers to respond and indicate if the transaction can be committed or rolled back.
The default value is 0, which sets the value to approximately twice the default
transaction-timeoutvalue with a maximum value of 120 seconds. This value provides backward compatibility for prior releases without this setting.If the specified value is -1, the maximum value supported by this attribute is used.
If the specified value exceeds the value set for
abandon-timeout-seconds, the value ofabandon-timeout-secondsis used.MBean Attribute:
JTAMBean.CompletionTimeoutSecondsMinimum value:
-1Maximum value:
2147483647
|