Unless you are doing one of the specific usage examples below, you will most likely NOT want to use this property.
Be careful when doing so as it is very possible to delete files other than log files if you are not careful.
This property controls the file pattern to purge old log files.
Every time when the log file is rolled and when a new log file is generated,
all files matching the specific pattern will be selected and sorted using the sort mode.
All available files will be queried and sorted with the specified mode, and files that exceed
the maximum number of log files will be deleted.
The pattern to purge files is specified here.
In this example, only the files whose names include 'wrapper-' and '.log' are going to be purged.
As the PIDs included in the file names are not sequential, sorting by their name would not result in what you expect.
So, the log files are sorted by their modification time (TIMES).
Following the rolling mode (SIZE_OR_JVM), log files will be rolled automatically
whenever the JVM is restarted or the log file size grows to the maximum size.
When the log file is rolled, ".1" and ".2" will be appended by the
Usage Example: Log files including the Wrapper's start time
It is also possible to create log files whose names include the start time of the Wrapper.
The following example will generate log files that include the Wrapper's start time.
These files can be sorted by their names rather than modification times.
The only benefit to using names rather than times is
that the files will be preserved correctly even if they are modified.