[logback-dev] [JIRA] Commented: (LBCLASSIC-265) Logging stops if invalid xml configuration is loaded by scanner

[Ceki Gulcu (JIRA)]

    [ http://jira.qos.ch/browse/LBCLASSIC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12038#action_12038 ] 

Ceki Gulcu commented on LBCLASSIC-265:
--------------------------------------

There might be undesirable side effects even when running joran a temporary context. For example, a RollingFileAppender might open/close an existing file as a result of running a config file. Another strategy is to memorize a safe configuration script  and fallback to it if the current configuration file is bogus. However, *correctly* determining that a configuration file is bogus or alternatively safe can be rather difficult.

> Logging stops if invalid xml configuration is loaded by scanner
> ---------------------------------------------------------------
>
>                 Key: LBCLASSIC-265
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-265
>             Project: logback-classic
>          Issue Type: Bug
>    Affects Versions: 0.9.28
>            Reporter: Iwein Fuld
>            Assignee: Logback dev list
>
> When logging with scan="true" it is possible to stop all logging of an application silently.
> Steps to reproduce:
> - start an application with valid configuration and scan=true
> - break the logback.xml (leave out a quote or something)
> -> log goes silent
> Expected behavior:
> Logger fails to load new config and keeps running on the old configuration (like when valid xml, but invalid configuration is loaded).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira