Gus Kormeier wrote:
Not sure if our installation is the same or not, but we are also using
Tomcat.
I had a similiar problem last week, it occurred after Tomcat went through a
hard restart and some software errors had the website hammered.
I found the lock file in /usr/local/tomcat/temp/ using loca
: 'Lock obtain timed out' even though NO locks exist...
James Dunn wrote:
>Which version of lucene are you using? In 1.2, I
>believe the lock file was located in the index
>directory itself. In 1.3, it's in your system's tmp
>folder.
>
>
Yes... 1.3 and I hav
James Dunn wrote:
Which version of lucene are you using? In 1.2, I
believe the lock file was located in the index
directory itself. In 1.3, it's in your system's tmp
folder.
Yes... 1.3 and I have a script that removes the locks from both dirs...
This is only one process so it's just fine t
Kevin A. Burton wrote:
Actually this is exactly the problem... I ran some single index tests
and a single process seems to read from it.
The problem is that we were running under Tomcat with diff webapps for
testing and didn't run into this problem before. We had an 11G index
that just took a
[EMAIL PROTECTED] wrote:
It is possible that a previous operation on the index left the lock open.
Leaving the IndexWriter or Reader open without closing them ( in a finally
block ) could cause this.
Actually this is exactly the problem... I ran some single index tests
and a single process see
Which version of lucene are you using? In 1.2, I
believe the lock file was located in the index
directory itself. In 1.3, it's in your system's tmp
folder.
Perhaps it's a permission problem on either one of
those folders. Maybe your process doesn't have write
access to the correct folder and
It is possible that a previous operation on the index left the lock open.
Leaving the IndexWriter or Reader open without closing them ( in a finally
block ) could cause this.
Anand
-Original Message-
From: Kevin A. Burton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 28, 2004 2:57 PM
