Hi Mike,
You were right I had 2 IndexWriters. I've checked again and it turned out I
had 2 IndexManagers loaded by 2 different classloaders, so even if stored
it in static Map, it didn't help.
Anyway thanks for help. But I have last question. Is it correct if I use
IndexSearcher during wrking In
Here is Lucene log with first exceptions that occured (FSDirectory with
NativeFSLockFactory).
IFD [Thread-79]: setInfoStream
[EMAIL PROTECTED]
IW 4 [Thread-79]: setInfoStream:
dir=org.apache.lucene.store.FSDirectory@/tmp/content/3615.0-3618.0
autoCommit=true
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ra
The strange thing is that when I use only FSDirectory with
SimpleFSLockFactory I don't see any exception (or I couldn't reproduce the
problem). FSDirectory with NativeFSLockFactory doesn't work as well as my
implementation of Directory and Lock (based on java.nio).
Hmmm, I don't see the reason of
I've checked unlock ant it is not called until exception occurs.
BTW, I' ve tried to use FSDirectorectory with NativeFSLockFactory and I
didn't get
LockObtainFailedException. I removed also this part making unlocking
(IndexReader.unlock).
The exception is:
Exception in thread "Thread-95"
org.apa
Hi Mike,
I'm sharing one instance of IndexManager across all threads and as I've
noticed only this one is used during indexing.
I'm unlocking before every indexing operation to make sure it would be
possible.
When IndexWriter is closed I assume it releases the lock and finishes its
work.
Does Ind
Hi,
I'm sometimes receiving FileNotFoundExceptions during indexing.
java.io.FileNotFoundException: /tmp/content/3615.0-3618.0/_3p.fnm (No such
file or directory)
at
com.test.vcssearch.DefaultServiceIndexer$2.run(DefaultServiceIndexer.java:245)
at java.lang.Thread.run(Thread.java:5
