Hi, I was able to track this issue down in my scenario and I'll provide a diff later today. In my case I am using Websphere 6.1 and Lucene 2.3.0. It would appear that there is a variable conflict that is only present when utilizing Lucene 2.3.0, refCount, the reference counter is used in JackRabbit's CachingMultiIndexSearch and in Lucene's IndexReader.
If you make the following changes to CachingMultiIndexSearch the issue appears to be resolved: * Comment out line 64 `private int refCount = 1` * Replace line 159 with `incRef()` * Replace lines 168-170 with `super.doClose()` IndexReader 2.3.0 has the variable refCount and this is the variable that is checked and results in the thrown exception. CachingMultiIndexSearch has the same variable and increments it accordingly, failing to increment the parent class's variable. Hope that helps, Sean On Jan 29, 2008 3:23 AM, Ard Schrijvers <[EMAIL PROTECTED]> wrote: > Hello, > > pls do send the test case (do you have a unit test??) > > Regards Ard > > > > Hi, > > > > I have the same issue. It seems that the only XPATH query > > that is working is "//*". Anything else will fail with the > > same exception. I can pack a test case (libraries included) > > and send it. > > > > Julien > > -- > > View this message in context: > > http://www.nabble.com/Lucene-AlreadyClosedException-tp15049132 > > p15152752.html > > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > > > > >
