[
http://jira.qos.ch/browse/LBCLASSIC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12012#action_12012
]
Ralph Goers commented on LBCLASSIC-265:
---------------------------------------
I have mentioned this before. Even if there is nothing wrong with the new
configuration there is still a timeframe where there is no logging
configuration in effect and all logging is disabled. There is currently no
good way to fix this in Logback due to how Loggers and the configuration are
co-mingled. This is something I have fixed in my experimental implementation of
Log4J 2.0 at Apache.
> 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
