In TIBCO Spotfire Server versions 7.11 and 7.12, if you change the SizeBasedTriggeringPolicy setting in the log4j2.xml configuration file from the location "<server-installation>tomcat\spotfire-config\log4j2.xml", the TIBCO Spotfire Server may may ignore reading this configuration file but instead reads the file from "<server installation>\tomcat\webapps\spotfire\WEB-INF\classes\log4j2.xml". Because of this, the logs file generated will be of the default size (20MB) instead of the manually configured option in "<server-installation>tomcat\spotfire-config\log4j2.xml". In general, no changes made in '<server-installation>tomcat\spotfire-config\log4j2.xml' are used.

The reason why it is picking the configuration file from a different location is that there is a defect in Spotfire dependency jar in versions 7.11 and 7.12 which is reading the log configuration from "<server installation>\tomcat\webapps\spotfire\WEB-INF\classes\".

This article provides a workaround for SizeBasedTriggeringPolicy issue in spotfire server versions 7.11 and 7.12

Windows, Linux

To resolve, upgrade to 7.13 or higher.

For versions 7.11 and 7.12, in order to ensure that the server reads the correct configuration file, you can specify the log4j2 configuration file location manually in catalina.properties per the instructions below:

1. Open catalina.properties under the directory "<server-installation>\tomcat\conf"
2. Edit the file and add the below line at the last

log4j.configurationFile=../spotfire-config/log4j2.xml

3. Restart TIBCO Spotfire Server service
 

KB: How to increase the log files retention period on the TIBCO Spotfire Server

• https://support.tibco.com/s/article/How-to-increase-the-log-files-retention-period-on-the-spotfire-server