Two segments finished today, one just fine and parses fine.
The other one fetched with -noParsing, failed although not on the same spot.
I'm attaching the output received with ctrl-break.
Because the first segment went fine, would I be right in assuming that
something's wrong with my RAM?
-----Original Message-----
From: Andrzej Bialecki [mailto:[EMAIL PROTECTED]
Sent: Friday, August 19, 2005 9:51 AM
To: [email protected]
Subject: Re: Nutch 0.7 released
EM wrote:
> The only difference from the previous configuration was that I enabled the
> "js" parser. However, one crash happened at a pdf file and I don't know
> about the other one. Unfortunately, the urls were not saved at the time.
The thread dumps that you sent don't point immediately to anything
obvious. There are always two threads waiting somewhere in httpclient
code, waiting for connection release, but that's normal, it's the way it
works.
Please try to run your fetches (on the same segments that hung before,
just delete everything except for fetchlist/), but this time with
-noParsing option. This way we should be able to eliminate problems
related to parsing.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
"MultiThreadedHttpConnectionManager cleanup" daemon prio=5 tid=0x0324ae38
nid=0x24b8 in Object.wait() [376f000..376fd8c]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <0x14e0ab78> (a java.lang.ref.ReferenceQueue$Lock)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$ReferenceQueueThread.run(MultiThreadedHttpConnectionManager.java:1100)
"fetcher0" prio=5 tid=0x031f2e68 nid=0x14d4 in Object.wait() [332f000..332fd8c]
at java.lang.Object.wait(Native Method)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:509)
- locked <0x14e0abf8> (a
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$ConnectionPool)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:394)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:393)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at
org.apache.nutch.protocol.httpclient.HttpResponse.<init>(HttpResponse.java:102)
at
org.apache.nutch.protocol.httpclient.Http.getProtocolOutput(Http.java:204)
at org.apache.nutch.fetcher.Fetcher$FetcherThread.run(Fetcher.java:135)
"Signal Dispatcher" daemon prio=10 tid=0x00a004c8 nid=0x26c4 waiting on
condition [0..0]
"Finalizer" daemon prio=9 tid=0x009fd8b0 nid=0x17dc in Object.wait()
[2f5f000..2f5fd8c]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <0x14d07dd0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x009fc530 nid=0x1cd4 in Object.wait()
[2f1f000..2f1fd8c]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:429)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
- locked <0x14d07e38> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x000369d8 nid=0x23d4 waiting on condition [7f000..7fc38]
at java.lang.Thread.sleep(Native Method)
at org.apache.nutch.fetcher.Fetcher.run(Fetcher.java:351)
at org.apache.nutch.fetcher.Fetcher.main(Fetcher.java:488)
"VM Thread" prio=5 tid=0x00a3b5f8 nid=0x19f0 runnable
"VM Periodic Task Thread" prio=10 tid=0x00a56c70 nid=0x1b1c waiting on condition
"Suspend Checker Thread" prio=10 tid=0x009ffa78 nid=0x213c runnable
