You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/03/01 06:18:55 UTC

[jira] Closed: (MRM-941) log4j config fails to log all errors

     [ http://jira.codehaus.org/browse/MRM-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-941.
----------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 1.4)
         Assignee: Brett Porter

> log4j config fails to log all errors
> ------------------------------------
>
>                 Key: MRM-941
>                 URL: http://jira.codehaus.org/browse/MRM-941
>             Project: Archiva
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: 1.1.1
>            Reporter: Max Bowsher
>            Assignee: Brett Porter
>
> The current log4j config fails to log all errors. For example, my database update job was failing because of a ClassFormatException thrown when the index-public-methods consumer tried to parse an invalid classfile, but no mention appeared in the log.
> This should be fixed as follows:
> 1. An <appender-ref ref="rolling"/> should be placed in the <root> logger.
> 2. The <appender-ref ref="rolling"/> should be removed from all the other <logger>s.
> 3. The attribute additivity="false" should be added to the <logger name="org.apache.archiva.AuditLog"> so that the audit logging does not go to the rolling appender despite it being configured on the root logger.
> After this is done, any packages which are overly noise at info-level can be selectively overridden to warn-level.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira