Use this page to specify settings for the transaction service. The transaction service is a server runtime component that can coordinate updates to multiple resource managers to ensure atomic updates of data. Transactions are started and ended by applications or the container in which the applications are deployed.
To view this administrative console page, click Servers > Application Servers > server_name > Container Services > Transaction Service.
The default maximum time, in seconds, that a transaction that is started by this server can remain inactive before the transaction service ends it. Any transaction that does not begin completion processing before this timeout occurs is rolled back.
This timeout is used only if the application component does not set its own transaction timeout.
The upper limit of this timeout is constrained by the maximum transaction timeout. For example, if you set a value of 500 for the total transaction lifetime timeout, and a value of 300 for the maximum transaction timeout, transactions will timeout after 300 seconds.
If you set this timeout to 0, the timeout does not apply and the value of the maximum transaction timeout is used instead.
Data type | Integer |
Units | Seconds |
Default | 120 |
Range | 0 to 2 147 483 647 |
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 being rolled back in this application server.
If you set this value to 0, there is no timeout limit.
Data type | Integer |
Units | Seconds |
Default | 60 |
Range | 0 to 2 147 483 647 |
Specifies whether the application server will log about-to-commit-one-phase-resource events from transactions that involve both 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-phase and two-phase commit resources. No additional records are written for transactions that do not involve a one-phase commit resource.
Data type | Check box |
Default | Cleared |
Range |
|
The default maximum time, in seconds, that a transaction that is started by this server can remain inactive before the transaction service ends it. Any transaction that does not begin completion processing before this timeout occurs is rolled back.
This timeout is used only if the application component does not set its own transaction timeout.
The upper limit of this timeout is constrained by the maximum transaction timeout. For example, if you set a value of 500 for the total transaction lifetime timeout, and a value of 300 for the maximum transaction timeout, transactions will timeout after 300 seconds.
If you set this timeout to 0, the timeout does not apply and the value of the maximum transaction timeout is used instead.
Data type | Integer |
Units | Seconds |
Default | 120 |
Range | 0 to 2 147 483 647 |
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 being rolled back in this application server.
If you set this value to 0, there is no timeout limit.
Data type | Integer |
Units | Seconds |
Default | 60 |
Range | 0 to 2 147 483 647 |
Specifies the number of transactions that are imported and prepared but not yet committed.
If there are transactions that have been imported and prepared but not yet committed, you can click the Review link to display a list of those transactions on the Transactions imported and prepared panel.
Data type | Integer |
Default | 0 |