index was locked because of InterruptedException [LUCENE-4097]

the index was locked, because of InterruptedException,and i could do nothing but restart tomcat,
how could i avoid this happen again?
thanks

this is stacktrace:
org.apache.lucene.util.ThreadInterruptedException: java.lang.InterruptedException
at org.apache.lucene.index.IndexWriter.doWait(IndexWriter.java:4118)
at org.apache.lucene.index.IndexWriter.waitForMerges(IndexWriter.java:2836)
at org.apache.lucene.index.IndexWriter.finishMerges(IndexWriter.java:2821)
at org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:1847)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1800)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1764)
at org.opencms.search.CmsSearchManager.updateIndexIncremental(CmsSearchManager.java:2262)
at org.opencms.search.CmsSearchManager.updateIndexOffline(CmsSearchManager.java:2306)
at org.opencms.search.CmsSearchManager$CmsSearchOfflineIndexThread.run(CmsSearchManager.java:327)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at org.apache.lucene.index.IndexWriter.doWait(IndexWriter.java:4116)
... 8 more

---
Migrated from [LUCENE-4097](https://issues.apache.org/jira/browse/LUCENE-4097) by wang, updated Jun 01 2012

Start with the stack-trace entry points in org.apache.lucene.index.IndexWriter, especially doWait, waitForMerges, finishMerges, and closeInternal, then trace the calling paths in org.opencms.search.CmsSearchManager. Reproduce the InterruptedException during index closing if possible; done should identify a reliable way to avoid or recover from the locked-index condition.

Written by the indexing model from the issue text.