TransactionService

Configuration of the transaction service.

Inherits from type Service and adds the following.

Attributes Summary
transactionLogDirectory : StringSpecifies the name of a directory for this server where the transaction service stores log files for recovery.
totalTranLifetimeTimeout : intThe maximum duration, in seconds, for transactions on this application server.
clientInactivityTimeout : intThe maximum duration, in seconds, between transactional requests from a remote client.
maximumTransactionTimeout : int@since 6.
heuristicRetryLimit : int@since 6.
heuristicRetryWait : int@since 6.
waitForCommitOutcome : boolean@since 6.
enableLoggingForHeuristicReporting : booleanEnables logging for heuristic reporting (an advanced function available in the EEx add-on package).
LPSHeuristicCompletion : LPSHeuristicCompletionKind@since 6.
propogatedOrBMTTranLifetimeTimeout : int@for zOS only

Attribute Details

transactionLogDirectory    -    Specifies the name of a directory for this server where the transaction service stores log files for recovery.
     data type:  String
     default Value:   unspecified



totalTranLifetimeTimeout    -    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.
     data type:  int
     default Value:   unspecified



clientInactivityTimeout    -    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.
     data type:  int
     default Value:   unspecified



maximumTransactionTimeout    -    @since 6.0.0Maximum 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.
     data type:  int
     default Value:   unspecified



heuristicRetryLimit    -    @since 6.0.0The 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.
     data type:  int
     default Value:   0



heuristicRetryWait    -    @since 6.0.0The 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.
     data type:  int
     default Value:   0



waitForCommitOutcome    -    @since 6.0.0Indicates 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.
     data type: boolean
     default Value:   false
     Allowed Values:  true   false  



enableLoggingForHeuristicReporting    -    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
     data type: boolean
     default Value:   false
     Allowed Values:  true   false  



LPSHeuristicCompletion    -    @since 6.0.0The 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).
     data type: LPSHeuristicCompletionKind
     default Value:   ROLLBACK
     Allowed Values:  ROLLBACK   COMMIT   MANUAL  



propogatedOrBMTTranLifetimeTimeout    -    @for zOS only
     data type:  int
     default Value:   unspecified


Copyright IBM Corp. 1997-2004