Memory management
Spotfire Statistics Services manages the job database size and the data/requests directory size by conducting periodic cleanup.
The frequency of the cleanup is controlled by the properties db.cleanup.run.interval.minutes and db.cleanup.time.to.live.days, which are set in the file spserver.properties.
By default, the value of db.cleanup.run.interval.minutes is set to 0, and the value of db.cleanup.time.to.live.days is set to 7 days. If the Spotfire Statistics Services instance has a large number of jobs submitted, then the memory allotted for database storage can exceed its maximum limit. This results in the error java.lang.OutOfMemoryError: GC overhead limit exceeded, which is written to the SplusServer.log. The amount of database memory configured for Spotfire Statistics Services (either the default or the custom-configured value) is not sufficient to perform the clean up of the number of jobs submitted over the period between configured cleanups.
To address this potential problem, you can either increase the memory allotted for the database on the Tomcat server, or you can reduce the number of days between cleanup.
- Increasing the database memory size on the Tomcat server
If you encounter an out-of-memory error between regular cleanup intervals, consider increasing the memory allotted on the Tomcat server for the Spotfire Statistics Services database. - Modifying the cleanup frequency
If you encounter Java out-of-memory errors, or if your data/requests directory gets very large, during regular cleanup intervals, then consider automating and fine-tuning the database and data/requests directory cleanup process .