Programmatically added loggers lost due to automatic reconfiguration

I use Log4j 2.9.1 with the XML configuration. A monitorInterval is specified in the XML config in order to reconfigure log4j, e.g. for debugging. Besides the XML configuration some loggers and appendes are created dynamically in Java. Problem: The dynamically added loggers and appenders are lo

Re: Programmatically added loggers lost due to automatic reconfiguration

Michael, On 9/29/17 8:30 AM, Michael Heinen wrote: > I use Log4j 2.9.1 with the XML configuration. A monitorInterval is > specified in the XML config in order to reconfigure log4j, e.g. for > debugging. > Besides the XML configuration some loggers and appendes are created > dynamically in Java. >

Issue with log4jConfiguration setting

Hi, With log4j2 v 2.9.1 (same issue in previous version 2.6), by putting the log4j2.xml file in WEB-INF/classes, log4j will eventually locate that config file as 'file:/' ConfigLocationUri: file:/opt/tomcat/webapps/log4jTest/WEB-INF/classes/log4j2.xml and the config file monitoring WIL

Re: Logging previous messages based on current messages?

I was looking at RoutingAppender. Is this a good class to look at if I wanted to implement a buffering appeder which calls other appenders? On Wed, Sep 13, 2017 at 3:43 PM, Ralph Goers wrote: > Please see https://issues.apache.org/jira/browse/LOG4J2-1137 >

Re: Logging previous messages based on current messages?

Sure, why not? Ralph > On Sep 29, 2017, at 6:19 PM, Sean McCauliff wrote: > > I was looking at RoutingAppender. Is this a good class to look at if I > wanted to implement a buffering appeder which calls other appenders? > > On Wed, Sep 13, 2017 at 3:43 PM, Ralph Goers