Hi devs,
When the --J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS system property is
set, the server/locator ignores the log level specified in the custom
Log4J configuration file at the startup. Is this expected behavior?
I could only find one note related to the above property in the "change
loglevel" command document
https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html
:
"When using a custom Log4J configuration, this command takes effect only
if the member whose logging level you want to change was started using
the --J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS system property."
From this note, it is not clear what other effects of this system
property are besides allowing this command to execute. I observed in
tests that the geode log-level parameter (e.g., start server
--log-level=debug) and custom Log4J log-level parameter (e.g., <Logger
name="org.apache.geode" level="DEBUG">) are mutually exclusive. Users
can choose between these two options with the LOG_LEVEL_UPDATE_OCCURS
system property. Is this a correct understanding?
Best Regards,
Jakov
