[
https://issues.apache.org/jira/browse/NUTCH-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549341#comment-14549341
]
Lewis John McGibbney commented on NUTCH-2013:
---------------------------------------------
[~markus17] no it is not. The patch for NUTCH-1934 was committed post 1.10
release as I knew there would be something wrong with it ;) I took your advice
and committed post 1.10
Thanks
Lewis
> 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
> Assignee: 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)
