If log-file has a value then Geode will register and configure LogWriterAppender during startup. Nulling out the value of log-file might work for you but I haven't actually tried it out.
Changing Geode to not use LogWriterAppender if a custom log4j2.xml is specified might be a good change or feature request as well. On Mon, May 14, 2018 at 3:28 AM, <[email protected]> wrote: > Hi, > > I am currently looking to configure Geode (standalone) to use custom > logging as per the documentation at https://geode.apache.org/docs/ > guide/15/managing/logging/configuring_log4j2.html. The motivation behind > this is to use a consistent logging pattern across all of our applications > as well as specifying a time based rolling policy. > > I have specified the -Dlog4j.configurationFile property accordingly and > the logs are output as I would expect using the custom configuration. > However, there still appears to be a default "locator.log" file created > despite not explicitly setting any of the log-* properties. By the looks of > the logs a default value for the log-file property is being set by the > Launcher. > > Please can you confirm if it is the expected behaviour to have two log > files? I was expecting to see a single log file based on the custom > configuration defined in the log4j2.xml file. If the expectation is that > there will be two log files (one based on log4j2.xml and another based on > default log-* properties) then am I supposed to specify log-* properties in > addition to log4j2.xml to control the default file (i.e. max file size, > disk space limit etc)? If these properties are set, will there be any > impact the logging behaviour defined in log4j2.xml? > > Thanks in advance, > Phil >
