The embedded Apache Tomcat server that is used in all of the SAS^® Viya™ web applications maintains a cache of web resources to minimize disk I/O. By default, Tomcat uses a maximum cache size of 10 MB, and entries are evicted after a time-to-live (TTL) setting has been reached. Because the static content never changes, SAS presets this TTL setting to 1 year, effectively making the caching unlimited. However, some web applications might exceed the maximum cache size and start to produce messages in the log similar to the following:

To alleviate the problem, you can reduce the TTL to a smaller number. SAS recommends setting the TTL to 43200 (12 hours) to prevent these messages from appearing in the logs.

If a service is producing the log messages, follow the steps below to alleviate the situation:

1. Set the TTL for the service that is producing the log messages. For example, for the SASVisualAnalytics service, set the TTL in the following command:
   curl -X PUT http://localhost:8500/v1/kv/config/SASVisualAnalytics/sas.servlet.container.cache.ttl -d '43200 ' -H "X-Consul-Token: consul-token"
   The value for consul-token is obtained from the client.token file in /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/.
   
   For the example above, the command with the consul-token value looks similar to the following:
   curl -X PUT http://localhost:8500/v1/kv/config/SASVisualAnalytics/sas.servlet.container.cache.ttl -d '43200' -H "X-Consul-Token: 29c4700f-ea89-41cd-8bc4-4198ccaa5bf9"
2. Restart the service by submitting the following command:
   service sas-viya-sasvisualanalytics-default restart

This problem affects only services that are deployed as WAR files. Those services include SASHome, SASLogon, SASVisualAnalytics, SASEnvironmentManager, SASThemeDesigner, SASVisualDataBuilder, and associated links.

Operating System and Release Information