Hi,

I'm having this problem when I try to search something after my tomcat
is runing for 2 or 3 days.
Just after build the index and start tomcat, everything is fine, but
after sometime  ( I couldn't find what is the trigger), I start to
have this exception.

here is the stack:

java.io.IOException: File does not exist
        at net.nutch.fs.LocalFileSystem.open(LocalFileSystem.java:77)
        at net.nutch.io.SequenceFile$Reader.<init>(SequenceFile.java:143)
        at net.nutch.io.SequenceFile$Reader.<init>(SequenceFile.java:136)
        at net.nutch.io.MapFile$Reader.<init>(MapFile.java:171)
        at net.nutch.io.MapFile$Reader.<init>(MapFile.java:160)
        at net.nutch.io.ArrayFile$Reader.<init>(ArrayFile.java:37)
        at 
net.nutch.searcher.FetchedSegments$Segment.getParseText(FetchedSegments.java:74)
        at 
net.nutch.searcher.FetchedSegments.getSummary(FetchedSegments.java:131)
        at 
net.nutch.searcher.FetchedSegments.getSummary(FetchedSegments.java:140)
        at net.nutch.searcher.NutchBean.getSummary(NutchBean.java:240)
....

It tries to open my segment dir to get the summary. I openned the
index with Luke, and the segment name in the index is right! It really
exists in my disk. Its readble, etc. So, why can't nutch read it?

I've found a bug at sun reporting that after sometime, the "user.dir"
(default in the nutch-default.xml) is lost by the JVM:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4117557

it seams that getCanonicalPath() prints the write directory, but the
other functions in File.class wont access the write one.

Did anyone have this problem?

[]s
Leonardo Barbosa

Reply via email to