Transaction service settings

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 .

Configuration tab

Transaction log directory

Specifies the name of a directory for this server where the transaction service stores log files for recovery.For the z/OS® platform, specifies the location of the JTA Partner Log.

Set this property to change the log file directory for an application server in one of the following scenarios:
  • If the applications use distributed resources or XA transactions; for example, multiple databases and resources are accessed within a single transaction.
  • If you configured your system for high availability of transactions. In this scenario, the transaction log directory must be accessible by all servers in the cluster, and must also be unique within the cluster.

    In a high availability (HA) environment, both the transaction log and the compensation log directory for each server in a cluster must be unique.

If you do not specify this directory during server configuration, the transaction log uses a default that is based on your installation directory: app_server_root)/ tranlog/cell_ name/node_ name/server_ name.

When an application that runs on the application server accesses more than one resource, the application server stores transaction information in the product directory so that it can coordinate and manage the distributed transaction correctly. When there is a higher transaction load, storing persistent information in this way can slow the performance of the application server because it depends on the operating system and the underlying storage systems. To achieve better performance, designate a new directory for the log files on a separate, physically larger, storage system.

If your application server demonstrates one or more of the following symptoms, change the transaction log directory:
  • CPU use remains low despite an increase in transactions
  • Transactions fail with several timeouts
  • Transaction rollbacks occur with the exception "Unable to enlist transaction"
  • The application server stops in the middle of a run and must be restarted
  • The disk that the application server is running on shows higher use
There are the following recommendations for a storage system for the log files:
  • Store log files on a redundant array of independent disks (RAID)

    In RAID configurations, the task of writing data to the physical media is shared across the multiple drives. This technique yields more concurrent access to storage for persisting transaction information, and faster access to that data from the logs. Depending upon the design of the application and storage subsystem, performance gains can range from 10% to 100%, or more in some cases.

  • Do not store log files with the operation system I/O mode set to concurrent I/O (CIO)

    When you designate a transaction log directory, ensure that the file system uses only synchronous write-through and write serialization operations. Some operating systems, such as AIX® JFS2, support an optional concurrent I/O (CIO) mode where the file system does not enforce serialization of write operations. On these systems, do not use CIO mode for application server transaction recovery log files.

To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the disk space allocation for the transaction log files, specified in kilobytes (nK) or megabytes (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.

;file_size   <!-- This format keeps the default directory -->
directory_name;file_size
dir://directory_name/directory_name;file_size
/directory_name/directory_name;file_size

For more information about transaction log sizes, see Managing transaction logging for optimum server availability.

Data type String
Default Initial value is the app_server_root/tranlog/cell_name/node_name/server_name 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.

On z/OS, this log is used for recovery of XA resources. When the application that runs on the WebSphere® product accesses XA resources, the WebSphere product stores information about the resource to enable XA transaction recovery. Use the following syntax:

[location type URL tag] location_specificationwhere
  • location type URL tag specifies the optional location type for the JTA Partner Log:
    • The default is dir://, which specifies that the JTA Partner Log location is in a fully qualified HFS directory specified by location_specification.
  • location specification specifies the location name for the JTA Partner Log:
    • To specify a logstream, use the syntax logstream://HLQ
      If your application server installation followed the convention of configuring logstreams to the coupling facility (CF), the logstream is named according to the syntax HLQ.server.X, where HLQ is a user-defined value between 1-8 characters specified in the installation dialog. Use this HLQ value to specify the JTA Partner Log location.
      Avoid trouble Avoid trouble: Set AUTODELETE(NO) for any logstreams.gotcha
    • If the location type URL tag is dir://, use a fully qualified HFS directory for the location specification. The complete name of the directory must be unique in the WebSphere node.

The default is dir://app_server_root/tranlog/server name.

To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the new disk space allocation for the transaction log files, specified in KB (nK) or MB (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.

dir://directory_name/directory_name;file_sizeK
/directory_name/directory_name;file_sizeK
;file_sizeK   <!-- This keeps the default directory -->

If you migrate a WebSphere Application Server Version 5 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 Version 5 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

The default maximum time, in seconds, allowed for a transaction that is started on this server before the transaction service initiates timeout completion. 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.

[z/OS] After the timeout occurs, transactions are allowed to continue running for a grace period of approximately four minutes. If the transaction is committed or rolled back during the grace period, the outcome of the transaction is always rolled back. If the transaction does not complete after the grace period, the controller abnormally ends the servant region in which the application component is running, with ABEND EC3 RSN=04130002 or 04130005.
Note: Only the total transaction lifetime timeout and the maximum transaction timeout have grace periods. You can disable the grace periods using the DISABLE_TRANSACTION_TIMEOUT_GRACE_PERIOD custom property.

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 time out 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

[AIX HP-UX Linux Solaris Windows] [iSeries] 0 to 2 147 483 647

Range

[z/OS] 0 to 2 147 040

Asynchronous response timeout

Specifies the amount of time, in seconds, that the server waits for an inbound Web Services Atomic Transaction (WS-AT) protocol response before resending the previous WS-AT protocol message.

Data type Integer
Units Seconds
Default 30
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 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

Maximum transaction timeout

Specifies the upper limit of the transaction timeout, in seconds, for transactions that run in this server. This value should be greater than or equal to the total transaction timeout. Specifies the maximum time to complete, in seconds, for transactions that run in this server. This value should be greater than or equal to the total transaction lifetime timeout [Updated in November 2011] AND greater than or equal to the application component timeout. If the maximum transaction timeout is set to a value less than either the total transaction lifetime timeout or the application component timeout, application component transactions that may require more time will timeout when the maximum transaction timeout is reached. [Updated in November 2011]

nov2011

This timeout constrains the upper limit of all other transaction timeouts. The following table shows how the different timeouts apply to transactions running in the server.
Table 1. Transaction timeouts
Timeout Transactions affected
Maximum transaction timeout All transactions running in this server that are not affected by the total transaction lifetime timeout or an application component timeout. These transactions include transactions imported from outside this server, such as those imported from a client.
Total transaction lifetime timeout All transactions that originated in this server that are not affected by an application component timeout, in other words, the associated application component does not set its own timeout.
Application component timeout Transactions that are specific to an application component.

You cannot set this transaction timeout using the administrative console.

If the component is a container-managed bean, set this timeout in the deployment descriptor for the component. For example, you can use an assembly tool, such as the Rational® Application Developer.

If the component is a bean-managed bean, set this timeout programmatically using the UserTransaction.setTransactionTimeout method.

Restriction: You cannot set the Application component timeout for an EJB 3.0 module with the Feature Pack for EJB 3.0. For more information, see the Feature Pack for EJB 3.0 limitations topic.

If you set a timeout to 0, that timeout does not apply, and is effectively disabled. If you set all timeouts to 0, transactions never time out.

For example, consider the following timeout values:
Table 2. Example timeout values
Timeout Value
Maximum transaction timeout 360
Total transaction lifetime timeout 240
Application component timeout 60
In this example, transactions that are specific to the application component time out after 60 seconds, other local transactions time out after 240 seconds, and any transactions that are imported from outside this server time out after 360 seconds. If you then change the application component timeout to 500, application component transactions time out after 360 seconds, the value of the maximum transaction timeout. If you set the maximum transaction timeout to 0, application component transactions time out after 500 seconds. If you remove the application component timeout, application component transactions time out after 240 seconds.

To determine the occurrence of a timeout as quickly as possible and to prevent further resource locking, WebSphere Application Server prevents further transactional work on the transactional path where the timeout condition has taken place. This applies equally to attempting to perform work under the current transaction context and to attempting to perform work under a different transactional context.

Data type Integer
Units Seconds
Default 300
Range 0 to 2 147 483 647
Range 0 to 2 147 040

Heuristic retry limit

Specifies the number of times that the application server retries a completion signal, such as commit or rollback. Retries occur after a transient exception from a resource manager or remote partner, or if the configured asynchronous response timeout expires before all Web Services Atomic Transaction (WS-AT) partners have responded.

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.

During recovery of a subordinate server in a distributed transaction, when the number of heuristic retries is exceeded, the heuristic completion direction property specifies how the transaction is completed.

Data type Integer
Default 0
Range 0 to 2 147 483 647

A value of 0 (the default) means try repeatedly forever.

Heuristic retry wait

Specifies 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

[AIX HP-UX Linux Solaris Windows] [iSeries] A value of 0 means that the application server determines the retry wait; the server doubles the retry wait after every 10 failed retries.

[z/OS] If you leave this value at 0, the application server still makes subsequent attempts to complete the transaction. It incrementally lengthens the wait time before each attempt, to improve system throughput.

Enable logging for heuristic reporting

[AIX HP-UX Linux Solaris Windows] [iSeries]

Specifies whether the application server logs 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.

[AIX HP-UX Linux Solaris Windows] [iSeries]
Data type Check box
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

Specifies the direction that is 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.

The heuristic completion direction property specifies how a transaction is completed in the following situations:
  • The transaction manager reports a heuristic outcome for a last participant support (LPS) resource.
  • The heuristic retry limit is exceeded during the recovery of a subordinate server in a distributed transaction.
  • The transaction is imported from a Java EE Connector Architecture (JCA) provider.

This property applies only to transactions that are in the situations just described.

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.

Enable file locking

Specifies whether the use of file locks is enabled when opening the transaction service recovery log.

If you enable this setting, a file lock will be obtained before accessing the transaction service recovery log files. File locking is used to ensure that, in a highly available WebSphere Application Server deployment, only one application server can access a particular transaction service recovery log at any one time. This setting has no effect in a standard deployment where you have not configured high availability support.
Attention: This setting requires a compatible network file system, such as network file system version 4, to operate correctly.
Data type Check box
Default Selected

Enable protocol security

Specifies whether the secure exchange of transaction service protocol messages is enabled.

This setting has no effect unless you enable WebSphere Application Server security on the server.

Data type Check box
Default Selected

HTTP proxy prefix

Specifies the external endpoint URL information that should be used for WS-AtomicTransaction and WS-BusinessActivity service endpoints. This should be in the form http://hostname[:port] where hostname may be the hostname of an HTTP proxy to this server.

Set this field if you are using an intermediary node, such as an HTTP server or Proxy Server for WebSphere, to send requests that comply with the Web Services Atomic Transaction or Web Services Business Activity protocols. The format for the prefix is as follows:
http://host_name:port
where
  • host_name is the host name used by clients to contact the Web service
  • port is the port for which the service is configured to accept client requests

If the intermediary node is not a Proxy Server, the prefix must be unique for each server. If you are using a Proxy Server, prefixes can be the same for each server in a cluster, because the Proxy Server determines dynamically which server to forward the request to.

The HTTPS prefix will be used if WebSphere Application Server security is enabled and protocol security is enabled for the transaction service, otherwise the HTTP prefix will be used.

Data type String
Default None

HTTPS proxy prefix

Specifies the external endpoint URL information that should be used for WS-AtomicTransaction and WS-BusinessActivity service endpoints. This should be in the form https://hostname[:port] where hostname may be the hostname of an HTTPS proxy to this server.

Set this field if you are using an intermediary node, such as an HTTP server or Proxy Server for WebSphere, to send requests that comply with the Web Services Atomic Transaction or Web Services Business Activity protocols. The format for the prefix is as follows:
https://host_name:port
where
  • host_name is the host name used by clients to contact the Web service
  • port is the port for which the service is configured to accept client requests

If the intermediary node is not a Proxy Server, the prefix must be unique for each server. If you are using a Proxy Server, prefixes can be the same for each server in a cluster, because the Proxy Server determines dynamically which server to forward the request to.

The HTTPS prefix will be used if WebSphere Application Server security is enabled and protocol security is enabled for the transaction service, otherwise the HTTP prefix will be used.

Data type String
Default None

Runtime tab

Transaction log directory

Specifies the name of a directory for this server where the transaction service stores log files for recovery.For the z/OS® platform, specifies the location of the JTA Partner Log.

Set this property to change the log file directory for an application server in one of the following scenarios:
  • If the applications use distributed resources or XA transactions; for example, multiple databases and resources are accessed within a single transaction.
  • If you configured your system for high availability of transactions. In this scenario, the transaction log directory must be accessible by all servers in the cluster, and must also be unique within the cluster.

    In a high availability (HA) environment, both the transaction log and the compensation log directory for each server in a cluster must be unique.

If you do not specify this directory during server configuration, the transaction log uses a default that is based on your installation directory: app_server_root)/ tranlog/cell_ name/node_ name/server_ name.

When an application that runs on the application server accesses more than one resource, the application server stores transaction information in the product directory so that it can coordinate and manage the distributed transaction correctly. When there is a higher transaction load, storing persistent information in this way can slow the performance of the application server because it depends on the operating system and the underlying storage systems. To achieve better performance, designate a new directory for the log files on a separate, physically larger, storage system.

If your application server demonstrates one or more of the following symptoms, change the transaction log directory:
  • CPU use remains low despite an increase in transactions
  • Transactions fail with several timeouts
  • Transaction rollbacks occur with the exception "Unable to enlist transaction"
  • The application server stops in the middle of a run and must be restarted
  • The disk that the application server is running on shows higher use
There are the following recommendations for a storage system for the log files:
  • Store log files on a redundant array of independent disks (RAID)

    In RAID configurations, the task of writing data to the physical media is shared across the multiple drives. This technique yields more concurrent access to storage for persisting transaction information, and faster access to that data from the logs. Depending upon the design of the application and storage subsystem, performance gains can range from 10% to 100%, or more in some cases.

  • Do not store log files with the operation system I/O mode set to concurrent I/O (CIO)

    When you designate a transaction log directory, ensure that the file system uses only synchronous write-through and write serialization operations. Some operating systems, such as AIX® JFS2, support an optional concurrent I/O (CIO) mode where the file system does not enforce serialization of write operations. On these systems, do not use CIO mode for application server transaction recovery log files.

To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the disk space allocation for the transaction log files, specified in kilobytes (nK) or megabytes (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.

;file_size   <!-- This format keeps the default directory -->
directory_name;file_size
dir://directory_name/directory_name;file_size
/directory_name/directory_name;file_size

For more information about transaction log sizes, see Managing transaction logging for optimum server availability.

Data type String
Default Initial value is the app_server_root/tranlog/cell_name/node_name/server_name 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.

On z/OS, this log is used for recovery of XA resources. When the application that runs on the WebSphere® product accesses XA resources, the WebSphere product stores information about the resource to enable XA transaction recovery. Use the following syntax:

[location type URL tag] location_specificationwhere
  • location type URL tag specifies the optional location type for the JTA Partner Log:
    • The default is dir://, which specifies that the JTA Partner Log location is in a fully qualified HFS directory specified by location_specification.
  • location specification specifies the location name for the JTA Partner Log:
    • To specify a logstream, use the syntax logstream://HLQ
      If your application server installation followed the convention of configuring logstreams to the coupling facility (CF), the logstream is named according to the syntax HLQ.server.X, where HLQ is a user-defined value between 1-8 characters specified in the installation dialog. Use this HLQ value to specify the JTA Partner Log location.
      Avoid trouble Avoid trouble: Set AUTODELETE(NO) for any logstreams.gotcha
    • If the location type URL tag is dir://, use a fully qualified HFS directory for the location specification. The complete name of the directory must be unique in the WebSphere node.

The default is dir://app_server_root/tranlog/server name.

To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the new disk space allocation for the transaction log files, specified in KB (nK) or MB (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.

dir://directory_name/directory_name;file_sizeK
/directory_name/directory_name;file_sizeK
;file_sizeK   <!-- This keeps the default directory -->

If you migrate a WebSphere Application Server Version 5 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 Version 5 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

The default maximum time, in seconds, allowed for a transaction that is started on this server before the transaction service initiates timeout completion. 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.

[z/OS] After the timeout occurs, transactions are allowed to continue running for a grace period of approximately four minutes. If the transaction is committed or rolled back during the grace period, the outcome of the transaction is always rolled back. If the transaction does not complete after the grace period, the controller abnormally ends the servant region in which the application component is running, with ABEND EC3 RSN=04130002 or 04130005.
Note: Only the total transaction lifetime timeout and the maximum transaction timeout have grace periods. You can disable the grace periods using the DISABLE_TRANSACTION_TIMEOUT_GRACE_PERIOD custom property.

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 time out 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

[AIX HP-UX Linux Solaris Windows] [iSeries] 0 to 2 147 483 647

Range

[z/OS] 0 to 2 147 040

Asynchronous response timeout

Specifies the amount of time, in seconds, that the server waits for an inbound Web Services Atomic Transaction (WS-AT) protocol response before resending the previous WS-AT protocol message.

Data type Integer
Units Seconds
Default 30
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 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

Maximum transaction timeout

Specifies the upper limit of the transaction timeout, in seconds, for transactions that run in this server. This value should be greater than or equal to the total transaction timeout. Specifies the maximum time to complete, in seconds, for transactions that run in this server. This value should be greater than or equal to the total transaction lifetime timeout [Updated in November 2011] AND greater than or equal to the application component timeout. If the maximum transaction timeout is set to a value less than either the total transaction lifetime timeout or the application component timeout, application component transactions that may require more time will timeout when the maximum transaction timeout is reached. [Updated in November 2011]

nov2011

This timeout constrains the upper limit of all other transaction timeouts. The following table shows how the different timeouts apply to transactions running in the server.
Table 1. Transaction timeouts
Timeout Transactions affected
Maximum transaction timeout All transactions running in this server that are not affected by the total transaction lifetime timeout or an application component timeout. These transactions include transactions imported from outside this server, such as those imported from a client.
Total transaction lifetime timeout All transactions that originated in this server that are not affected by an application component timeout, in other words, the associated application component does not set its own timeout.
Application component timeout Transactions that are specific to an application component.

You cannot set this transaction timeout using the administrative console.

If the component is a container-managed bean, set this timeout in the deployment descriptor for the component. For example, you can use an assembly tool, such as the Rational® Application Developer.

If the component is a bean-managed bean, set this timeout programmatically using the UserTransaction.setTransactionTimeout method.

Restriction: You cannot set the Application component timeout for an EJB 3.0 module with the Feature Pack for EJB 3.0. For more information, see the Feature Pack for EJB 3.0 limitations topic.

If you set a timeout to 0, that timeout does not apply, and is effectively disabled. If you set all timeouts to 0, transactions never time out.

For example, consider the following timeout values:
Table 2. Example timeout values
Timeout Value
Maximum transaction timeout 360
Total transaction lifetime timeout 240
Application component timeout 60
In this example, transactions that are specific to the application component time out after 60 seconds, other local transactions time out after 240 seconds, and any transactions that are imported from outside this server time out after 360 seconds. If you then change the application component timeout to 500, application component transactions time out after 360 seconds, the value of the maximum transaction timeout. If you set the maximum transaction timeout to 0, application component transactions time out after 500 seconds. If you remove the application component timeout, application component transactions time out after 240 seconds.

To determine the occurrence of a timeout as quickly as possible and to prevent further resource locking, WebSphere Application Server prevents further transactional work on the transactional path where the timeout condition has taken place. This applies equally to attempting to perform work under the current transaction context and to attempting to perform work under a different transactional context.

Data type Integer
Units Seconds
Default 300
Range 0 to 2 147 483 647
Range 0 to 2 147 040

Manual transactions

Specifies the number of transactions that await manual completion by an administrator.

If there are transactions awaiting manual completion, you can click the Review link to display a list of those transactions on the Transactions needing manual completion panel.

Data type Integer
Default 0

Retry transactions

Specifies the number of transactions with some resources being retried.

If there are transactions with resources being retried, you can click the Review link to display a list of those transactions on the Transactions retrying resources panel.

Data type Integer
Default 0

Heuristic transactions

Specifies the number of transactions that have completed heuristically.

If there are transactions that have completed heuristically, you can click the Review link to display a list of those transactions on the Transactions with heuristic outcome panel.

Data type Integer
Default 0

Imported prepared transactions

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



Subtopics
Related concepts
Web Services transactions, firewalls and intermediary nodes
Related tasks
[Fix Pack 17 or later] Configuring last participant support for an application server
Disabling file locking
Configuring transaction properties for an application server
Related reference
Feature Pack for EJB 3.0 limitations
Related information
Compensation service settings
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=Transaction_service
File name: udat_contranserv.html