This topic explains how to configure session state log files in VMware Tanzu GemFire.
Several log files are written by the various parts of the session management code.
cacheserver.log. Log file written by the Tanzu GemFire server process.gemfire_modules.log. Log file written by the Tanzu GemFire cache client.
Adding Additional Debug Logging to the Tanzu GemFire Server Log
To add fine-level logging to the Tanzu GemFire cache server, add the log-level property to the server process. For example:
gfsh> start server --name=server1 --cache-xml-file=../conf/cache-server.xml --log-level=fine
This adds fine-level logging to the server.log file.
Note: This can assist when debugging Tanzu GemFire server issues, but adds a large number of log messages to the file.
Add Debug Logging to gemfire_modules.log
To add fine-level logging to the Tanzu GemFire Cache Client, add the log-level property to the Listener element in the Tomcat server.xml file. For example:
<Listener log-level="fine"
cache-xml-file="${gemfire-cs.cache.configuration.file}"
className="org.apache.geode.modules.session.catalina.ClientServerCacheLifecycleListener"
criticalHeapPercentage="${gemfire-cs.critical.heap.percentage}"
evictionHeapPercentage="${gemfire-cs.eviction.heap.percentage}"
log-file="${gemfire-cs.log.file}"
statistic-archive-file="${gemfire-cs.statistic.archive.file}"
statistic-sampling-enabled="${gemfire-cs.statistic.sampling.enabled}"/>
This adds fine-level logging to the file defined by the ${gemfire-cs.log.file} property. The default log file name is gemfire_modules.log.
Note:
This can assist when debugging Tanzu GemFire client issues, but adds a large number of log messages to the file.
