SWS: Exceeded maxLifeSeconds: xxxx messagse in the Agent logs.

Products

• Workspace Streaming (formerly AppStream)

Issue/Introduction

What are the Exceeded maxLifeSeconds: xxxx messagse in the Agent logs.

Cause

We look at checkForRemoval().  This code shows that if the log Boolean "isInfoEnabled" is set to be true, every time we find an item that reaches its endOfLife they will log that statement and then remove that item from from the cache.

This is an informational logging statement that normally won't appear. Logging is set too high in Apache configuration.

SWS uses JCS for LDAP calls and for Database calls, JCS is a generic in-memory memory caching library.

Resolution

Set the appache loggin on the FrontEnds and the STE to not be debug/INFO. 

In the STE.conf on the STE/BE server there are some log4j setttings and the default is set to:

log4j.category.org.apache= WARN, ALL_APPENDER

If it is set to DEBUG or INFO the apache tomcat will put its information or debug messages in there that has no impact on the streaming environment. The recommanded setting is WARN or ERROR to limit extra messages from being printed in the logs.