Thanks, Chris! (And thank you, Andrzej for interpreting my rantings!)
That plan sounds fantastic and I would be happy to help out.
Scott
On Jun 5, 2006, at 1:01 PM, Chris Mattmann wrote:
Hi Andrzej,
The main problem, as Scott observed, is that the static flag
affects all
instances of
[
http://issues.apache.org/jira/browse/NUTCH-258?page=comments#action_12414762 ]
Scott Ganyo commented on NUTCH-258:
---
For the record: I strongly object to closing this issue for the following
reasons:
1) Having a *side-effect* of the entire system stop
[ http://issues.apache.org/jira/browse/NUTCH-283?page=all ]
Scott Ganyo updated NUTCH-283:
--
Attachment: patch.txt
There was a typo in the earlier patch. This patch supersedes the first patch.
If the Fetcher times out and abandons Fetcher Threads, severe
: Nutch
Type: Bug
Components: fetcher
Versions: 0.8-dev
Reporter: Scott Ganyo
Attachments: patch.txt
If a Fetcher has chosen to time out and has abandoned outstanding Fetcher
Threads, resources that those Fetcher Threads may be using are closed. This
naturally causes any
[ http://issues.apache.org/jira/browse/NUTCH-283?page=all ]
Scott Ganyo updated NUTCH-283:
--
Attachment: patch.txt
If the Fetcher times out and abandons Fetcher Threads, severe errors will
occur on those Threads
Environment: All
Reporter: Scott Ganyo
Priority: Critical
Once a SEVERE log item is written, Nutch shuts down any fetching forevermore.
This is from the run() method in Fetcher.java:
public void run() {
synchronized (Fetcher.this) {activeThreads++;} // count threads
