Re: Weird NPE in RAMInputStream when merging indices

2003-10-22 Thread Otis Gospodnetic
That's why I emphasized that Hashtable doesn't allow nulls. If this is happening often, then yes, that is the thing to be suspicious about, and is easily to test by modifying your local copy of RAMDirectory. Otis --- petite_abeille <[EMAIL PROTECTED]> wrote: > Hi Otis, > > On Wednesday, Oct 22,

Re: Weird NPE in RAMInputStream when merging indices

2003-10-22 Thread petite_abeille
Hi Otis, On Wednesday, Oct 22, 2003, at 18:06 Europe/Amsterdam, Otis Gospodnetic wrote: Since 'files' is a Hashtable, neither the key nor the value (file) can be null, even though the NPE in RAMInputStream constructor implies that file was null. Yep... pretty weird... but looking at openFile(Str

Re: Weird NPE in RAMInputStream when merging indices

2003-10-22 Thread Otis Gospodnetic
Hm, beat me. The code in question seems to be: public RAMInputStream(RAMFile f) { file = f; length = file.length; } ...which is called from: /** Returns a stream reading an existing file. */ public final InputStream openFile(String name) { RAMFile file = (RAMFile)files.get(na

Weird NPE in RAMInputStream when merging indices

2003-10-21 Thread petite_abeille
Hello, What could cause such weird exception? RAMInputStream.: java.lang.NullPointerException java.lang.NullPointerException at org.apache.lucene.store.RAMInputStream.(RAMDirectory.java:217) at org.apache.lucene.store.RAMDirectory.openFile(RAMDirectory.java:182) at org.apache.lucene.index.FieldIn