NonStop Server Guide for BEA WebLogic Server 8.1

HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001
5-1
5 Configuring JTA
Java™ Transaction API (JTA) elements of the configuration describe several attributes
for controlling the WebLogic Server transaction manager. If the TMF configuration is
different for your application, the JTA attributes can be changed. This is an example
with some NonStop server-specific changes.
<JTA
AbandonTimeoutSeconds=”7200”
MaxTransactions=”1000”
CheckpointIntervalSeconds=”60”
ForgetHeuristics=”true”
Name=”examples”
/>
The following are explanations of the JTA attributes specified above:
AbandonTimeoutSeconds
Number of seconds after which a transaction is abandoned if not complete. TMF
defaults the autoabort timeout to 7200 seconds, making it sensible to restrict the
WebLogic Server AbandonTimeout to be the same as TMF.
MaxTransactions
Controls the maximum number of transactions that can execute concurrently.
When a static TMF resource manager is configured, the maximum number of
transactions that can be started is restricted by the TFILE depth. The TFILE depth
is 1000.
Since the WebLogic Server can create transaction table entries on startup to
recover indoubt transactions, this parameter should be set to a higher value than
the maximum number of concurrent TMF transactions. The default value is 10000
and can be left unchanged without negative performance impact.
CheckpointIntervalSeconds
The default value is 300 seconds (5 minutes). The transaction manager creates
new TLOG files and checks old TLOG files for deletion at this interval.
This attribute has the side effect of determining the interval at which a registered
XA resource is polled for in-doubt transactions. The correct behavior for a
transaction manager is to call the recover on a resource manager immediately
after it registers so that the resource manager can remove locks and be available
for general transaction processing.