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

Ralph Goers commented on LBCLASSIC-265:
---------------------------------------

The key is that I don't have to roll back. Unlike Log4j 1.x and Logback the 
configuration is separate from the loggers created by getLogger(). This allows 
reconfiguration to be more or less atomic. If there is something wrong with the 
new configuration then nothing gets changed.  Once the new configuration is 
constructed then loggers are reset to point to the new configuration instead of 
the old one. Thus no logger is ever in a state where it is "unconfigured", 
although there will be a point in time where some loggers point to the old 
configuration and some to the new one.

Of course, you are welcome to go look at the code. While the core of the system 
functions it is far from complete.

> 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

        
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev

Reply via email to