[logback-dev] [JIRA] Commented: (LBCLASSIC-265) Logging stops if invalid xml configuration is loaded by scanner
Ceki Gulcu (JIRA)
noreply-jira at qos.ch
Thu Jun 23 23:55:51 CEST 2011
[ http://jira.qos.ch/browse/LBCLASSIC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12048#action_12048 ]
Ceki Gulcu commented on LBCLASSIC-265:
--------------------------------------
This issue is now fixed. See http://github.com/ceki/logback/commit/690ac09e30d01
Joran will remember well-formed configuration files. In case an XML/SAX parsing error occurs (in the new configuration file), Joran will fall back to previous configuration file. This should work even in case of included configuration files.
> 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: Ceki Gulcu
>
> 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
More information about the logback-dev
mailing list