Menu
▾
▴
#305 wrapper.logfile not properly implemented (or documented)
A bug seems to have been introduced in one of the recent (past year?) releases relating to logging. Either the documentation needs to be updated, or the behavior changed back to match it. The problem is with the 'wrapper.logfile' setting - its documentation says that if this set set to an empty string logging will be disabled. From what I can see this is no longer true - disabling is done by setting 'wrapper.logfile.loglevel=NONE' instead.
Thank you for reporting this issue.
This bug was introduced in version 3.5.31 released last march. An empty value is wrongly interpreted as the working directory. The Wrapper will thus show a warning and fall back to the default log file instead of just disabling the log:
WARN | wrapper | 2017/11/16 12:07:42 | Unable to write to the configured log file: C:\wrapper-windows-x86-64-3.5.31-pro\professional\bin (Access is denied. (0x5))
WARN | wrapper | 2017/11/16 12:07:42 | Falling back to the default file in the current working directory: C:\wrapper-windows-x86-64-3.5.31-pro\professional\bin\wrapper.log
This bug will be fixed in the next release to match with the behavior of version 3.5.30 and earlier.
As you mentionned it, the recommended way is to use wrapper.logfile.loglevel=NONE to disable the log file.
Thank you again for opening this issue.
Best Regards,
Maxime
Fixed in version 3.5.35