This type is a class for model objects.
Configuration of the transaction service.
Package: applicationserverAttributes Summary | |
transactionLogDirectory : EString | Specifies the name of a directory for this server where the transaction service stores log files for recovery. |
totalTranLifetimeTimeout : EInt | The maximum duration, in seconds, for transactions on this application server. Any transaction that is not requested to complete before this timeout will be rolled back. |
clientInactivityTimeout : EInt | 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. |
maximumTransactionTimeout : EInt | @since 6.0.0 Maximum time, in seconds, for any transactions that execute in the server. This constrains the upper limit of the transaction timeout for all transactions that execute on the server. This value should be greater than or equal to the total transaction timeout which is the default timeout for transactions started on the server. This limit will constrain timeout set programmatically by BMT beans and values imported with contexts received from foreign servers. |
heuristicRetryLimit : EInt | @since 6.0.0 The number of times the Transaction Manager will retry a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means retry forever. If the retry is abandonned then the resource/partner administrator becomes responsible for ensuring that the resource/partner?s branch is completed appropriately. The Transaction Manager will raise, on the resource/partner?s behalf, an XAException indicating a HeuristicHazard. If a commit was requested, the transaction originator will receive an exception on the commit operation; if the transaction is container-initiated, then the container will return a RemoteException/EJBException to the EJB client. |
heuristicRetryWait : EInt | @since 6.0.0 The number of seconds the Transaction Manager will wait before retrying a retriable completion signal (such as commit or rollback) following a transient exception from a Resource Manager/remote partner. A value of 0 (the default) means that the Transaction Manager will determine the retry wait. The retry wait will be doubled each time there have been 10 failed retries. |
waitForCommitOutcome : EBoolean | @since 6.0.0 Indicates whether the Transaction Manager should retry commit requests synchronously (true) or asynchronously (false) following a transient exception from a Resource Manager/remote partner. The default value of false (which is the unconfigurable behaviour of WebSphere Application Server 5.x and earlier) means that the retries will be asynchronous and the transaction originator can assume that the commit will succeed. A value of true means that the retries will be synchronous, blocking the processing of the commit request. If the heuristic retry limit is exceeded, then a HeuristicMixed exception will be returned to the transaction originator. If the transaction is container initiated, then the container will return a RemoteException/EJBException to the EJB client. |
enableLoggingForHeuristicReporting : EBoolean | Enables logging for heuristic reporting (an advanced function available in the EEx add-on package). If applications are configured to allow one-phase resources to participate in two-phase 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 will be perfomed for any transaction that involves both one and two-phase resources. No additional records are written for transactions that do not involve a one-phase resource. Default=false |
LPSHeuristicCompletion : LPSHeuristicCompletionKind | @since 6.0.0 The heuristic completion action to be taken by the Transaction Service in an LPS transaction when the outcome of the 1PC resource is unknown. (EEx function only) The default behaviour is to rollback the 2PC resources. A setting of MANUAL means the Transaction Service will take no action and leave the 2PC resources in-doubt pending and administrative completion (eg via the Admin Console). |
propogatedOrBMTTranLifetimeTimeout : EInt | @for zOS only |
enableFileLocking : EBoolean | Enable NFS file locking |
enableProtocolSecurity : EBoolean | Enable security on transaction protocol messages |
asyncResponseTimeout : EInt | Timeout in seconds for responses to WS-AT protocol messages |
httpProxyPrefix : EString | Prefix of WS-Transaction Proxy for HTTP protocol |
httpsProxyPrefix : EString | Prefix of WS-Transaction Proxy for HTTPS protocol |
Attribute Details |