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

Posted to issues@archiva.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2008/01/08 10:11:00 UTC

[jira] Commented: (MRM-633) Logging is too verbose

    [ http://jira.codehaus.org/browse/MRM-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119120 ] 

Maria Odea Ching commented on MRM-633:
--------------------------------------

I've identified a couple of logging points which probably needs to be changed:
- revert the default log level for the repo scanner from debug to info. this could easily be switched to debug for debugging purposes, anyway.
- remove this line "logger.debug( "Sending to consumer: " + consumer.getId() );" from ConsumerProcessFileClosure since the consumer problem is logged when an error is encountered during processing.


> Logging is too verbose
> ----------------------
>
>                 Key: MRM-633
>                 URL: http://jira.codehaus.org/browse/MRM-633
>             Project: Archiva
>          Issue Type: Bug
>          Components: system
>    Affects Versions: 1.0
>            Reporter: Brett Porter
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.1
>
>
> the default Archiva logging generates about 160Mb of logs a day on my reasonably inactive, not large local instance. This is primarily due to scanning.
> In addition, the logs are duplicated in the archiva.log and wrapper.log file.

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