Re: NPE in RAMDirectory after upgrade to 2.1

2007-02-26 Thread Michael McCandless
"jm" <[EMAIL PROTECTED]> wrote: > You were right. As I have many indexes I keep a cache of the > IndexWriters, and in some specific case (that cannot happen in my dev > env) I was closing them without removing them from the cache. Somehow > it was working before 2.1, and upgrading made the error cl

Re: NPE in RAMDirectory after upgrade to 2.1

2007-02-26 Thread jm
Mike, You were right. As I have many indexes I keep a cache of the IndexWriters, and in some specific case (that cannot happen in my dev env) I was closing them without removing them from the cache. Somehow it was working before 2.1, and upgrading made the error clear. thanks javi On 2/26/07, M

Re: NPE in RAMDirectory after upgrade to 2.1

2007-02-26 Thread Michael McCandless
"jm" <[EMAIL PROTECTED]> wrote: > I have two processes running in parallel, each one adding and deleting > to its own set of indexes. Since I upgraded to 2.1 I am getting a NPE > at RAMDirectory.java line 207 in one of the processes. > > Line 207 is: > RAMFile existing = (RAMFile)fileMap.g

NPE in RAMDirectory after upgrade to 2.1

2007-02-26 Thread jm
Hello all, I have two processes running in parallel, each one adding and deleting to its own set of indexes. Since I upgraded to 2.1 I am getting a NPE at RAMDirectory.java line 207 in one of the processes. Line 207 is: RAMFile existing = (RAMFile)fileMap.get(name); the stack trace is: java