Log4J2 Defaultrolloverstrategy Delete Action Is Not Deleting Files Mới Update

There could be a few different reasons why the Log4j2 DefaultRolloverStrategy delete action is not deleting files. Here are some things you can check:

1. Permissions: Make sure that the user running the application has permission to delete files in the directory where the log files are stored. If the user doesn’t have permission, then the delete action will fail.

2. File names: Check the file names of the log files that you expect to be deleted. By default, the DefaultRolloverStrategy uses a pattern of “app-%d{MM-dd-yyyy}-%i.log.gz”. This means that log files will be named with the date they were created (in the format MM-dd-yyyy) and an index number. If the delete action is not finding the files you expect, it could be because they are named differently.

3. File location: Double-check that the log files are actually being stored in the directory you expect. It’s possible that they are being stored in a different location, which would explain why the delete action is not finding them.

4. Rollover settings: Make sure that the rollover settings are configured correctly. By default, the DefaultRolloverStrategy will rollover log files when they reach a certain size (based on the “fileSize” parameter), and will keep up to 7 rolled-over files (based on the “max” parameter). If the rollover settings are configured differently than you expect, it could be causing the delete action to not find the files you expect.

5. Log4j2 version: There have been some issues with the delete action in certain versions of Log4j2. Make sure that you are using a recent version of Log4j2, and that it is compatible with the version of Java you are running.

By checking these things, you should be able to determine why the delete action is not deleting files and take appropriate steps to resolve the issue.