The file size of the transaction manager log can impact SAS® Web Application Server performance


When the file size of the transaction manager log file for the SAS Web Application Server increases, that increase can impact the performance of SAS Web Application Server.

Symptoms

You might see the transaction manager log file for the SAS Web Application Server grow in size. Such an increase impacts the performance of the SAS Web Application Server. This issue can manifest as long start-up times for SASServer1_1, performance degradation of SAS® web applications, or both. 

The transaction manager log file is located here: SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/tmlognnnn.log (In this syntax, nnnn specifies a sequential number.)

This transaction manager log is used by the SAS Web Application Server while it is running, and it is normal for that file to fluctuate in size. Typically, the SAS Web Application Server should handle the cleanup of that file properly. However, when this issue occurs, you might see that file grow to hundreds of megabytes in size (or larger). 

Problem Resolution

If you experience this problem, you can clear that log file using the following steps:

  1. Stop the SAS Web Application Server instance that is impacted (typically SASServer1_1). In Microsoft Windows operating environments, stop SASServer1_1 using Windows Services. In Linux operating environment, use the following command to stop SASServer1_1:

    SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin/tcruntime-ctl.sh stop

  2. Delete the tmlognnnn.log file from the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/ directory. This is a good opportunity to delete all of the files in the logs directory, which you can do by using the appropriate command for your operating environment (show below):
    • Linux command: rm -f SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/*
    • Windows command: del SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/*

  3. Start the SAS Web Application Server instance that is impacted (typically, SASServer1_1). Under Windows, start the server instance using Windows Services. Under Linux, submit the following command:

    SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/bin/tcruntime-ctl.sh start

After you perform these steps, determine whether the performance issues have improved. If the issues are not resolved with these steps, or if you have any questions about the information in this note, contact SAS Technical Support.