[jira] Updated: (LOG4PHP-73) No output from logger after trunk update

["Johannes Skov Frandsen (JIRA)" <ji...@apache.org>]

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

Johannes Skov Frandsen updated LOG4PHP-73:
------------------------------------------

    Summary: No output from logger after trunk update  (was: No output from logger af trunk update)

> No output from logger after trunk update
> ----------------------------------------
>
>                 Key: LOG4PHP-73
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-73
>             Project: Log4php
>          Issue Type: Bug
>          Components: Code
>    Affects Versions: 2.0
>         Environment: osx, php 5.3
> osx, php 5.2.9
> linux , 5.2.10
>            Reporter: Johannes Skov Frandsen
>             Fix For: 2.0
>
>
> I updated from trunk this morning and now I get no output from my loggers.
> require_once $_SERVER['DOCUMENT_ROOT'].'lib/log4php/src/main/php/Logger.php';
> define('LOG4PHP_CONFIGURATION', $_SERVER['DOCUMENT_ROOT'].'/include/log4php.cron.properties');
> $logger = Logger::getLogger('AutoScan');
> This is my configuration:
> log4php.debug = true
> log4php.rootLogger = WARN, default
> log4php.appender.default = LoggerAppenderDailyFile
> log4php.appender.default.datePattern = Y-m-d
> log4php.appender.default.file = ../logs/system_%s.log
> log4php.appender.default.layout = LoggerLayoutTTCC
> log4php.logger.Scan = DEBUG, Scan, Scan2
> log4php.appender.Scan = LoggerAppenderDailyFile
> log4php.appender.Scan.layout = LoggerLayoutHtml
> log4php.appender.Scan.datePattern = Y-m-d
> log4php.appender.Scan.file = ../logs/Scan_%s.log
> log4php.appender.Scan2 = LoggerAppenderEcho
> log4php.appender.Scan2.layout = LoggerLayoutHtml
> log4php.logger.AutoScan = DEBUG, AutoScan
> log4php.appender.AutoScan = LoggerAppenderEcho
> log4php.appender.AutoScan.layout = LoggerLayoutHtml
> Any idea what could be the cause?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.