Open kingdomhit opened 4 months ago
@kingdomhit,
Sorry for the delay, your report slipped through our hands.
You are right the solution to #1445 provided by #1549 was not complete and it caused a regression.
The File.delete()
call can fail for two reasons:
false
to stop the rollover is the right behavior IMHO.true
.The problem could be solved by switching from the incoherent File
class to the new Path
class (see #2117).
I am adding this to the 2.25.0
milestone. If you could provide a PR we would happily review it (in a timely manner this time :wink:).
Description
In earlier versions, such as 2.18.0, even if log files are deleted accidentally, the deleted files are automatically generated when the rollback conditions are met. But now, it doesn't work when we use log4j 2.23.1.
name: ROLLING_FILE policies: sizeBasedTriggeringPolicy: {size: 100MB} timebasedtriggeringpolicy: {interval: '1'}
Configuration
Version: [Log4j version] 2.23.1 Operating system: [OS and version] linux JDK: [JDK distribution and version] JDK8
Logs
Reproduction
This commit : https://github.com/apache/logging-log4j2/commit/3bc608db0de95690ea0a75e2f6a290d9418d7bbc RollingFileManager private boolean rollover(final RolloverStrategy strategy) before: return true ---> Now: return success; After we rollback this change , it works.