logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude
Date Wed, 02 Mar 2016 18:35:18 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176196#comment-15176196

ASF GitHub Bot commented on LOG4J2-1301:

Github user garydgregory commented on the pull request:

    We are on Java 7 for now so we cannot use Java 8 features unless we do so in a way is
not used on Java 7.
    The bigger picture item is: If we invented a Log4j include mechanism that works across
all of our configuration formats (XML, JSON, YAML), then we would not need a new watchFiles
attribute for this used case because we would know which files to watch. We could even enable/disable
watching on a per-include basis:
    <Include monitorIntervalSeconds="60">file://...</Include>
    This monitorIntervalSeconds would override the value set on the Configuration element.
    Sorry, I am getting side tracked... I need to bring this up on the dev ML.

> Automatic reconfiguration with xml and xinclude
> -----------------------------------------------
>                 Key: LOG4J2-1301
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1301
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Alan Achtenberg
>         Attachments: GroupFileConfigurationMonitor.java, MyXmlConfiguration.java, MyXmlConfigurationFactory.java
> Automatic reconfiguration does not work with xinclude/xml.
> Modifying xinclude files is not detected as a file change on on the main config file
and as such it is not reconfigured when updates are made to files included with xinclude (ie.
> Desired functionality would be to also listen for changes of files that are included
by main configuration file as well and update the configuration as needed.
> An alternative would be to allow user to specify additional files to monitor for changes.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message