I agree that something is fishy with SizeAndTimeBasedRollingPolicy; we're probably going to have to fall back to just using size rotation until we figure out what's going on. The attached logback-richcar.xml file configures a monthly and 500M size limit rotation. The log is fairly heavily used and we often have multiple logs in a month. When the month changes, however, the last active log gets truncated and its records lost. This has happened at least twice. It's likely that records are written to the log when the monthly rotation occurs.Unable to embed resource: logback.xml of type application/xml |