[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4php-dev
Subject:    [jira] [Commented] (LOG4PHP-188) rootLogger logs although level isn't reached
From:       "Ivan Habunek (JIRA)" <jira () apache ! org>
Date:       2013-04-23 14:51:15
Message-ID: JIRA.12606566.1347019784633.208302.1366728675426 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/LOG4PHP-188?page=com.atlassian.jira.plugin \
.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639124#comment-13639124 ] 

Ivan Habunek commented on LOG4PHP-188:
--------------------------------------

Frankly, the logger hierarchy does not work very well. Especially when dynamically \
adding loggers. It should be improved.

If you think this is wrong, please open a new issue and add a reproducable scenario \
which demonstrates what is wrong. Otherwise, by the time someone gets around to \
fixing bugs for the next release, this might get overlooked.

And to answer your last question, log4php was created as a direct port of log4j, but \
we do not strive to be exactly the same.

                
> rootLogger logs although level isn't reached
> --------------------------------------------
> 
> Key: LOG4PHP-188
> URL: https://issues.apache.org/jira/browse/LOG4PHP-188
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.2.1
> Environment: Windows Server 2008 R2, IIS 7
> Reporter: Florian Platzer
> Assignee: Ivan Habunek
> Fix For: 2.2.1
> 
> Attachments: log4php.patch, test.php
> 
> 
> 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


[prev in list] [next in list] [prev in thread] [next in thread]