If this property is not specified,
then logging will be written to a file called "wrapper.log"
in the same directory as the Wrapper executable by the default.
Setting the property to a blank value will cause file logging to be disabled.
If the Wrapper is unable to write to the configured wrapper.logfile (e.g because of a permission issue), it would
fall back to a default log file in the working directory. If this would also
fail, the log file will be disabled and logging will only continue in the
console, syslog or EventLog. Starting from version 3.5.30, the Wrapper will resume logging
into the configured file as soon as it is available again. If the log file
had been disabled and the configured log file would still be locked, then it
will try to resume the logging in the default log file.
Log File Name generated by Tokens:
The specified log file name may be able to contain one or both of the tokens;
ROLLNUM and YYYYMMDD.
The ROLLNUM token is used when the log file is rolled.
If the format is "wrapper.log.ROLLNUM",
the "ROLLNUM" token is replaced with an integer,
and then the roll numbers will be appended to the end of the file name "wrapper.log".
The larger roll number values, the older files.
The most recent rolled log file will always have a roll number of "1",
which is "wrapper.log.1".
The second recent one will be "wrapper.log.2".
property has a rolling mode,
if a ROLLNUM token is not included in the specified log file,
".ROLLNUM" will be appended at the end by default.
Whenever either token does not apply to a given file name format,
it will be stripped from the generated file name. When a token part is stripped,
the preceding character will also be stripped if it is a ".", "-", or "_".