(sorry for the fat-fingered send earlier) Hello. Our environment depends on these things:
- programmatic log4j configuration - having "shutdownHook" disabled - ideally: not having to depend on the log4j.configurationFile environment var I've had a hard time balancing all three of them. Generally, the first access on the rootLogger context installs a default configuration that always enables the shutdownHook, and there's not a clear means to disable it without falling back to the log4j.configurationFile property. Some of the methods available for reconfiguration (onChange, setConfiguration), don't reset the shutdown hook. As a new user to the group, and out of curiosity, why does shutdownHook exist in the first place? It causes us to lose logs when the system is shutting down -- why is this on by default? On Wed, Jun 4, 2014 at 2:54 PM, James Bellenger <[email protected]> wrote: > Hello. > Our environment depends on two things: > > - programmatic log4j configuration > - having "shutdownHook" disabled > - ideally: not having to depend on the log4j.configurationFile > environment var > > programmatic configuration of log4j2. > In trying to remove any dependencies on the log4j.configurationFile env > variable, I've found that there's not a good way to ensure that there is >
