On Tue, 27 Apr 2010, Andi Vajda wrote:
On Tue, 27 Apr 2010, Shai Erera wrote:
But that's not a good explanation I think. Realtime protection is always
on,
and I agree w/ Mark - if NativeFSLock fails because of that, we should fix
that b/c Lucene is run on users' machines, where AV software is running
too.
Moreover, this happens very rarely for me ... I even ran the tests while
scanning the Temp folder at the same time, and it didn't happen.
I've had similar random failures on Mac OS X 10.6. They started happening
recently, about two weeks ago.
Here is a stacktrace:
======================================================================
ERROR: testWriteLock (lia.indexing.LockTest.LockTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/Users/vajda/apache/pylucene/samples/LuceneInAction/lia/indexing/LockTest.py",
line 45, in testWriteLock
writer1.close()
JavaError: org.apache.lucene.store.LockReleaseFailedException: failed to
delete
/private/var/folders/lp/lp2+7G9YFNapwTmv3E25uE+++TI/-Tmp-/index/write.lock
Java stacktrace:
org.apache.lucene.store.LockReleaseFailedException: failed to delete
/private/var/folders/lp/lp2+7G9YFNapwTmv3E25uE+++TI/-Tmp-/index/write.lock
at
org.apache.lucene.store.NativeFSLock.release(NativeFSLockFactory.java:311)
at
org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:1801)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1732)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1696)
Andi..
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
