Domains: Configuration: JTA

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

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

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

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

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

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

Specifies whether the transaction manager will automatically perform an XAResource 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

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

Specifies the security mode to use for XA calls in cross-domain transactions. Only applies to transactions in which some participating resources are running on older versions of WebLogic Server.

In previous releases of WebLogic Server, the transaction coordinator used the kernel identity when calling to remote resources, however calls were made over a non-secure channel. In the current release, remote calls made as the kernel identity must use a secure channel, which causes an interoperability problem with previous WebLogic domains and a possible performance problem in JTA with an admin channel enabled. The security interoperability mode setting enables you to control the XA call behavior.

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.

• performance

  - The transaction coordinator makes calls using anonymous at all times. This implies a small security risk since a malicious third party could then try to affect the outcome of transactions.

• compatibility

  - The transaction coordinator makes calls as the kernel identity over an insecure channel. This is a high security risk because it means that the server's kernel identity could be captured and used for nefarious purposes. However, this setting is required to interoperate with older, unpatched versions of WebLogic Server.

MBean Attribute:
JTAMBean.SecurityInteropMode