Details
-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: Mercury
-
Fix Version/s: Galileo
-
Component/s: None
-
Labels:None
Description
The aml.log file on AML24 is up to 17.6 GB and has entries way back to 2014-11-05. I have also seen this behavior in SAPI on pretty much every other server. It takes an unnecessarily long time to look into production issues when the log file is so large.
The server has definitely been restarted since the creation of this file.
The same tomcat server is correctly rolling over all the api logging which uses log4j instead of logback. Since the configuration for logback looks correct but just isn't working, maybe it is time to switch back to log4j since it works and is easier to configure.