[
https://issues.apache.org/jira/browse/LOG4PHP-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451300#comment-13451300
]
Christer Lindh commented on LOG4PHP-188:
----------------------------------------
Should recursion really stop if a logger is not enabled for that level, what if
there is another one further up with a matching level? But I could be wrong,
not sure about what the additivity rules are.
> rootLogger logs although level isn't reached
> --------------------------------------------
>
> Key: LOG4PHP-188
> URL: https://issues.apache.org/jira/browse/LOG4PHP-188
> Project: Log4php
> Issue Type: Question
> Components: Code
> Affects Versions: 2.2.1
> Environment: Windows Server 2008 R2, IIS 7
> Reporter: Florian Platzer
> Priority: Minor
>
> I downloaded the current version of log4php and used an existing
> configuration:
> rootLogger (level = FATAL, appender = echo)
> customLog (level = DEBUG, appender = dailyfile)
> When i log to customLog with DEBUG level, i also get the message printed on
> screen:
> Logger::getLogger('customLog')->debug('test');
> When I change rootLogger's appender to dailyfile, the message is logged twice
> in the log file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
