Use this page to modify transaction service settings.
To view this administrative console page, click Servers > Application Servers > server > Transaction Service.
Specifies the 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 log at startup as the directory (install_root)/tranlog/(server_name).
When an application running on WebSphere Application Server accesses more than one resource, Application Server stores transaction information within the product directory 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, designate a new directory for the log files on a separate, physically larger storage system.
Set this property to change your log file directory when the application server shows one or more of following signs:
File system recommendations:
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 even more in some cases.
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 whereby 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.
Data type | String |
Default | Initial value is the %WAS_HOME%/tranlog/(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. If disk input and output is low, but the server is still high, consider increasing the size of the log files. |
Specifies the maximum duration, in seconds, for transactions on this application server.
Any transaction that is not requested to complete before this time-out is rolled back. If set to 0, transactions never time out.
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 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 |