You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Ivan Habunek (JIRA)" <ji...@apache.org> on 2012/10/07 10:39:02 UTC

[jira] [Closed] (LOG4PHP-177) logger writes every message twice

     [ https://issues.apache.org/jira/browse/LOG4PHP-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Habunek closed LOG4PHP-177.
--------------------------------

    Resolution: Not A Problem
    
> logger writes every message twice
> ---------------------------------
>
>                 Key: LOG4PHP-177
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-177
>             Project: Log4php
>          Issue Type: Bug
>          Components: Code
>    Affects Versions: 2.2.1
>         Environment: windows 7, php 5.3 (bundled with xampp)
>            Reporter: Sagi Mann
>            Priority: Minor
>
> The following code and configuration logs everything twice, but is not expected to. This was attempted with both LoggerAppenderConsole and LoggerAppenderFile, maybe reproducible with other appenders as well. If I remove the <appender_ref> tag from the <logger name="MyClass"> element below, the issue no longer occurs, but AFAIU, this kind of workaround should not be required.
> log4php.xml:
> <configuration xmlns="http://logging.apache.org/log4php/">
>     <appender name="myAppender" class="LoggerAppenderConsole">
>     </appender>
>     <root>
>         <level value="WARN" />
>         <appender_ref ref="myAppender" />
>     </root>
>     <logger name="MyClass">
>         <level value="WARN" />
>         <appender_ref ref="myAppender" />
>     </logger>
> </configuration>
> index.php:
> Logger::configure('log4php.xml');
> class MyClass {
> 	protected $logger = null;
> 	public function __construct() { $this->logger = Logger::getLogger(get_class($this)); }
> 	public function f() { $this->logger->warn("f"); }
> }
> $cls = new MyClass();
> $cls->f();
> output:
> WARN - f
> WARN - f

--
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