You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (JIRA)" <ji...@apache.org> on 2015/05/18 16:06:00 UTC

[jira] [Updated] (NUTCH-2013) Fetcher: missing logs "fetching ..." on stdout

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

Sebastian Nagel updated NUTCH-2013:
-----------------------------------
    Attachment: NUTCH-2013-v1.patch

Patch to make all classes in the fetcher package pulled out from Fetcher to stand-alone classes to log to stdout as before.

> Fetcher: missing logs "fetching ..." on stdout
> ----------------------------------------------
>
>                 Key: NUTCH-2013
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2013
>             Project: Nutch
>          Issue Type: Bug
>          Components: fetcher
>    Affects Versions: 1.11
>            Reporter: Sebastian Nagel
>             Fix For: 1.11
>
>         Attachments: NUTCH-2013-v1.patch
>
>
> When running Fetcher no messages {{fetching ...}} do appear on stdout, there are only {{-activeThreads=10, ...}} messages. This is caused by the refactoring of Fetcher in NUTCH-1934:
> * logging class is now FetchThread but it is not configured to log to stdout in log4j.properties
> * alternatively, FetcherTread's LOG could still be obtained from Fetcher.class
> * other refactored classes could be affected as well (FetchItem, etc.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)