DirectWriteRolloverStrategy and SizeBasedTriggeringPolicy

[Class-New]

DirectWriteRolloverStrategy and SizeBasedTriggeringPolicy use, found that more than limit the size of the file size

[Class-New]

SizeBasedTriggeringPolicy size limit is 5 k，but the results are as follows
5.9K common.85.log
6.2K common.86.log
3.2K common.87.log

[ppkarwasz]

Hi @Class-New,

Apologies for the delayed response — we're doing our best to respond to all issues despite limited time, but occasionally some slip through the cracks.

Thank you for your report!

This behavior is actually expected and not a bug, but rather an implementation detail. As I explained in a recent Stack Overflow answer, Log4j Core enforces a 5 KiB limit on the active log file and rolls it over after that limit is exceeded. As a result, the rolled (archived) log file will contain the 5 KiB of existing log data plus the log event that triggered the rollover.

That said, this behavior isn't set in stone. If you’d prefer the rollover to happen before writing the triggering event—so that it lands in the new log file—you’re welcome to open a PR with that change. We’d be happy to review it!