[ https://issues.apache.org/jira/browse/LOG4J2-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory resolved LOG4J2-2068. ---------------------------------- Resolution: Fixed Fix Version/s: 2.9.2 In Git master. Please verify and fix. Adding a unit test would be greatly appreciated. > Can't set monitorInterval for composite XML configuration. > ---------------------------------------------------------- > > Key: LOG4J2-2068 > URL: https://issues.apache.org/jira/browse/LOG4J2-2068 > Project: Log4j 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.9.1 > Reporter: Robert Haycock > Fix For: 2.9.2 > > Attachments: patch_2068.diff > > > When trying to combine a composite configuration with automatic reload, it > fails to reload. > When an {{XmlConfiguration}} is reloaded it calls > {{XmlConfiguration.reconfigure()}} which sets the {{rootElement}} field, and > everything is fine. > When a {{CompositeConfiguration}} is reloaded, it doesn't call > {{reconfigure()}} on the {{XmlConfigurations}}. This means when it tries to > start the config {{XmlConfiguration.setup()}} is called and {{rootElement}} > is null, resulting in an error message "No logging configuration". > End result is the config isn't loaded and there's no more logging. > To reproduce, it doesn't matter what is in the configurations. Just need at > least 2 XML configs in the {{log4j.configurationFile}} property and the > {{monitorInterval}} set. > (Ps. my first ticket) -- This message was sent by Atlassian JIRA (v6.4.14#64029)