[
https://issues.apache.org/jira/browse/NUTCH-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836125#action_12836125
]
Hudson commented on NUTCH-719:
------------------------------
Integrated in Nutch-trunk #1074 (See
[http://hudson.zones.apache.org/hudson/job/Nutch-trunk/1074/])
fetchQueues.totalSize incorrect in Fetcher
> fetchQueues.totalSize incorrect in Fetcher2
> -------------------------------------------
>
> Key: NUTCH-719
> URL: https://issues.apache.org/jira/browse/NUTCH-719
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.0.0
> Reporter: Julien Nioche
> Assignee: Julien Nioche
> Fix For: 1.1
>
>
> I had a look at the logs generated by Fetcher2 and found cases where there
> were no active fetchQueues but fetchQueues.totalSize was != 0
> fetcher.Fetcher2 - -activeThreads=200, spinWaiting=200,
> fetchQueues.totalSize=1, fetchQueues=0
> since the code relies on fetchQueues.totalSize to determine whether the work
> is finished or not the task is blocked until the abortion mechanism kicks in
> 2009-03-12 09:27:38,977 WARN fetcher.Fetcher2 - Aborting with 200 hung
> threads.
> could that be a synchronisation issue? any ideas?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
