|Title|Lucene locking up
|Date|06-Sep-2005 20:41:49 EEST
|[Bug criticality]|BadBug
|Browser version|FireFox
|[Bug status]|ClosedBug
|[PageProvider] used|Versioned
|Servlet Container|Tomcat 5.5.9
|Operating System|WindowsXP
|Java version|1.4.2

This bug keeps coming back - after I get it once all Searches fail completely and the only way to "fix" it is to remove all Lucene files and force it to reindex the wiki - then some days later it happens again.

2005-09-06 13:34:59,991 [Thread-60] ERROR com.ecyrd.jspwiki.providers.CachingProvider  - Unable to update page 'Requirement_tsk_0' from Lucene index
java.io.IOException: Index locked for write: Lock@C:\home\jspwiki-repository\IrpWiki\work\lucene\write.lock
	at org.apache.lucene.index.IndexWriter.<init>(Unknown Source)
	at org.apache.lucene.index.IndexWriter.<init>(Unknown Source)
	at com.ecyrd.jspwiki.providers.CachingProvider.updateLuceneIndex(CachingProvider.java:743)
	at com.ecyrd.jspwiki.providers.CachingProvider.access$200(CachingProvider.java:71)
	at com.ecyrd.jspwiki.providers.CachingProvider$1.run(CachingProvider.java:376)
	at java.lang.Thread.run(Thread.java:595) 
----all of the quality checks we do for the primary one (DefaultURLConstructor). This is, for sure, a bug, and the right way to ferret it out is 

I get it too, but completely randomly (it seems).  Unfortunately, this is very hard to debug.  Maybe it's some sort of a concurrency issue?  Any Lucene experts around?  Any new library versions?  Workarounds?

-- JanneJalkanen

I personally have never seen this problem, has anyone seen this problem occuring the last few months on the current JSPWiki releases ?

If nobody has seen it, well let us close the bug, and re-open it if the problem occurs.