Transaction service settings
Use this page to modify transaction service settings.
To view this administrative console page, click...
Servers | Application Servers | servername | Container Services | Transaction Service
Configuration tab
- Transaction log directory
Name of a directory for this server where the transaction service stores log files for recovery.
A blank value in the server configuration is expanded by the transaction service at startup as the directory...
install_root/tranlog/cell/node/servernameWhen the application running on WebSphere Application Server accesses more than one resource, Application Server stores transaction information to properly coordinate and manage the distributed transaction. In a higher transaction load, this persistence slows down performance of the application server due to its dependency on the operating system and the underlying storage systems.
To achieve better performance, move the transaction log files to a storage device with more physical disk drives, or preferably RAID storage array disk drives. When the log files are moved to the file systems on such disks, the task of writing data to the physical media is shared across the multiple disk drives. This allows more concurrent access to persist transaction information and faster access to that data from the logs.
This change is applicable only to the configuration where the application uses distributed resources or XA transactions, for example, multiple databases and resources are accessed within a single transaction.
Consider setting this property when the application server shows one or more of following signs:
- CPU utilization remains low despite an increase in transactions
- Transactions fail with several timeouts
- Transaction rollbacks occur with unable to enlist transaction exception
- Application server hangs in middle of a run and requires the server to be restarted
- The disk on which an application server is running shows higher utilization
Data type String Default Initial value is the install_root/tranlog/cell/node/servername directory and a default size of 1MB. Recommended Create a file system with at least 3-4 disk drives raided together in a RAID-0 configuration. Then, create the transaction log on this file system with the default size. When the server is running under load, check the disk input and output. If disk input and output time is more then 5%, consider adding more physical disks to lower the value. If you migrate a WebSphere Application Server V5 node to Version 6, the stored location of this configuration property is moved from the server level to the node (server index) level. If you have specified a non-default log directory for a V5 application server, you are prompted to save the transaction service settings again, to confirm that you want the log directory saved to the node level.
- Total transaction lifetime timeout
Specifies the maximum duration, in seconds, for transactions on this application server.
Any transaction that is not requested to complete before this timeout is rolled back. If set to 0, only the maximum transaction timeout configuration value applies.
Data type Integer Units Seconds Default 120 Range 0 to 2 147 483 647 - Client inactivity timeout
Specifies the maximum duration, in seconds, between transactional requests from a remote client.
Any period of client inactivity that exceeds this timeout results in the transaction rolling back in this application server. If set to 0, there is no timeout limit.
Data type Integer Units Seconds Default 60 Range 0 to 2 147 483 647 - Maximum transaction timeout
Specifies the maximum duration, in seconds, that transactions started by or propagated into this application server are allowed to run.
This value limits the upper bound of all other transaction related timeouts. For example, if a component attempts to set a transaction timeout of 360 seconds, and the Maximum Transaction Timeout setting is 300 seconds, the Maximum Transaction Timeout setting of 300 seconds is used.
If set to 0, there is no limit and therefore the timeout specified by the Total transaction lifetime timeout property or component timeout is used.
Data type Integer Units Seconds Default 300 Range 0 to 2 147 040 - Heuristic retry limit
The number of times that the application server retries a completion signal, such as commit or rollback, after a transient exception from a resource manager or remote partner.
If the application server abandons the retries, then the resource manager or remote partner is responsible for ensuring that the resource or partner’s branch of the transaction is completed appropriately. The application server raises (on behalf of the resource or partner) an exception that indicates a heuristic hazard. If a commit was requested, the transaction originator receives an exception on the commit operation; if the transaction is container-initiated, then the container returns a remote exception or EJB exception to the EJB client.
Data type Integer Default 0 Range 0 to 2 147 483 647 A value of 0 (the default) means retry forever.
- Heuristic retry wait
The number of seconds that the application server waits before retrying a completion signal, such as commit or rollback, after a transient exception from a resource manager or remote partner.
Data type Integer Default 0 Range 0 to 2 147 483 647 A value of 0 means that the application server determines the retry wait; the server doubles the retry wait after every 10 failed retries.
- Enable logging for heuristic reporting
Select this property to enable the application server to log "about to commit one-phase resource" events from transactions that involve a one-phase commit resource and two-phase commit resources.
This property enables logging for heuristic reporting. If applications are configured to allow one-phase commit resources to participate in two-phase commit transactions, reporting of heuristic outcomes that occur at application server failure requires extra information to be written to the transaction log. If enabled, one additional log write is performed for any transaction that involves both one- and two-phase commit resources. No additional records are written for transactions that do not involve a one-phase commit resource.
Data type String Default Cleared Range
- Cleared
- The application server does not log "about to commit one-phase resource" events from transactions that involve a one-phase commit resource and two-phase commit resources.
- Selected
- The application server does log "about to commit one-phase resource" events from transactions that involve a one-phase commit resource and two-phase commit resources.
- Heuristic completion direction
The direction used to complete a transaction that has a heuristic outcome; either the application server commits or rolls back the transaction, or depends on manual completion by the administrator.
Data type Drop-down list Default ROLLBACK Range
- COMMIT
- The Application server heuristically commits the transaction.
- ROLLBACK
- The Application server heuristically rolls back the transaction.
- MANUAL
- The application server depends on an administrator to manually complete or roll back transactions with heuristic outcomes.
Runtime tab
- Transaction log directory
Name of a directory for this server where the transaction service stores log files for recovery.
A blank value in the server configuration is expanded by the transaction service at startup as the directory install_root/tranlog/cell/node/servername.
When the application running on WebSphere Application Server accesses more than one resource, Application Server stores transaction information to properly coordinate and manage the distributed transaction. In a higher transaction load, this persistence slows down performance of the application server due to its dependency on the operating system and the underlying storage systems.
To achieve better performance, move the transaction log files to a storage device with more physical disk drives, or preferably RAID storage array disk drives. When the log files are moved to the file systems on such disks, the task of writing data to the physical media is shared across the multiple disk drives. This allows more concurrent access to persist transaction information and faster access to that data from the logs.
This change is applicable only to the configuration where the application uses distributed resources or XA transactions, for example, multiple databases and resources are accessed within a single transaction.
Consider setting this property when the application server shows one or more of following signs:
- CPU utilization remains low despite an increase in transactions
- Transactions fail with several timeouts
- Transaction rollbacks occur with unable to enlist transaction exception
- Application server hangs in middle of a run and requires the server to be restarted
- The disk on which an application server is running shows higher utilization
Data type String Default Initial value is the install_root/tranlog/cell/node/servername directory and a default size of 1MB. Recommended Create a file system with at least 3-4 disk drives raided together in a RAID-0 configuration. Then, create the transaction log on this file system with the default size. When the server is running under load, check the disk input and output. If disk input and output time is more then 5%, consider adding more physical disks to lower the value. If you migrate a WebSphere Application Server V5 node to Version 6, the stored location of this configuration property is moved from the server level to the node (server index) level. If you have specified a non-default log directory for a V5 application server, you are prompted to save the transaction service settings again, to confirm that you want the log directory saved to the node level.
- Total transaction lifetime timeout
Specifies the maximum duration, in seconds, for transactions on this application server.
Any transaction that is not requested to complete before this timeout is rolled back. If set to 0, only the maximum transaction timeout configuration value applies.
Data type Integer Units Seconds Default 120 Range 0 to 2 147 483 647 - Client inactivity timeout
Specifies the maximum duration, in seconds, between transactional requests from a remote client.
Any period of client inactivity that exceeds this timeout results in the transaction rolling back in this application server. If set to 0, there is no timeout limit.
Data type Integer Units Seconds Default 60 Range 0 to 2 147 483 647 - Maximum transaction timeout
Specifies the maximum duration, in seconds, that transactions started by or propagated into this application server are allowed to run.
This value limits the upper bound of all other transaction related timeouts. For example, if a component attempts to set a transaction timeout of 360 seconds, and the Maximum Transaction Timeout setting is 300 seconds, the Maximum Transaction Timeout setting of 300 seconds is used.
If set to 0, there is no limit and therefore the timeout specified by the Total transaction lifetime timeout property or component timeout is used.
Data type Integer Units Seconds Default 300 Range 0 to 2 147 040 - Manual transactions
The number of transactions awaiting manual completion by an administrator.
If there are transactions awaiting manual completion, one can click the Review link to display a list of those transactions on the href="Transactions_needing_manual_completion.html">Transactions needing manual completion panel.
Data type Integer Default 0 - Retry transactions
The number of transactions with some resources being retried.
If there are transactions with resources being retried, one can click the Review link to display a list of those transactions on the href="Transactions_retrying_resources.html">Transactions retrying resources panel.
Data type Integer Default 0 - Heuristic transactions
The number of transactions that have completed heuristically.
If there are transactions that have completed heuristically, one can click the Review link to display a list of those transactions on the href="Transactions_with_heuristic_outcome.html">Transactions with heuristic outcome panel.
Data type Integer Default 0 - Imported prepared transactions
The number of transactions imported and prepared but not yet committed.
If there are transactions that have been imported and prepared but not yet committed, one can click the Review link to display a list of those transactions on the href="Transactions_imported_and_prepared.html">Transactions imported and prepared panel.
Data type Integer Default 0