Amadeus cookies policy - you'll see this message only once.

Amadeus use cookies on this website. They help us to know a little bit about you and how you use our website, which improves the browsing experience and marketing - both for you and for others. They are stored locally on your computer or mobile device. To accept cookies, continue browsing as normal. Or, go to the privacy policy for more information.

Cleaning Up Your Web Logs to Improve Start-Up Times for Web Applications

In a SAS® environment, it is expected that the SAS Web Applications can take up to 30 minutes to start.  This has been known on occasion to increase slowly over time, which can be caused by several factors.  One reason for this increase can be due to the size of the log files for the applications, and the number of temporary files stored on the server.  This can be easy to resolve by cleaning out these files on the server.  On one occasion, in an environment which took approximately 35 minutes to start all their Web Applications, after cleaning up the logs and temporary files, the Web Applications were fully started in less than five minutes.

Stop the SAS Services

To complete any of these clean-up steps, the following Middle-Tier SAS services will need to be stopped in the order presented:

  • SAS Deployment Agent
  • SAS Environment Manager Agent 
  • SAS Environment Manager server
  • All SAS Web Application Servers
  • SAS Web Server
  • Cache Locators 
  • DIP Job Runner

Once these services are stopped, the log files can be cleaned up for these applications.

Note: In some environments multiple Web Application Servers are present (e.g. SASServer1_1 and SASServer7_1 etc.) these must all be stopped to remove any locks on their log files.

1. JMS Broker

The first check which needs to be completed is to verify the size of the journal log files directory in the location:

<Config>\Levn\Web\activemq\data\kahadb

In a clean environment this will be typically around 35MB, however this can grow over time.  If the size of this folder is significantly higher, it is a good idea to clean up the contents of this.  Make sure that the contents of the following folder are removed, and the folder structure is left in place:

<Config>\Levn\Web\activemq\data\

2. Cache Locators

The Cache Locator appends log messages to a single file.  This file can become large over time and cleaning this can increase the performance on an environment.  Three logs can be removed on the SAS environment to improve the performance of the Cache Locator:

<Config>\Levn\Web\gemfire\instances\ins_xxx\gemfire.log
<Config>\Levn\Web\gemfire\instances\ins_xxx\gemfirecommand.log
<Config>\Levn\Web\gemfire\instances\ins_xxx\locatorXXXstate.dat

Note: XXX resolves to the port used for the Cache Locator instance, by default this would be 41415.

In some environments it is possible to have multiple Cache Locators on multiple servers. It is important to stop the service and remove these logs on all machines within an environment where these folders are present.

3. SAS Web Application Logs

Like the Cache Locator, the SAS Web Applications typically append new log entries to the end of a single log file.  These log files can become extremely large and it is advisable to clean these out regularly.  To complete this, all the content from the following folders can be safely removed:

<Config>\Levn\Web\Logs\SASServerX_X\
<Config>\Levn\Web\WebAppServer\SASServerX_X\logs\
<Config>\Levn\Web\WebAppServer\SASServerX_X\temp\

Start the SAS Services

The services can now be started again in the correct order:

  • DIP Job Runner
  • Cache Locators 
  • SAS Web Server
  • All SAS Web Application Servers
  • SAS Environment Manager server
  • SAS Environment Manager Agent 
  • SAS Deployment Agent