If this is a stupid question, I deeply apologize. I'm stumped.
I have a message-driven EJB using Lucene. In *every* case where the MDB is
trying to create an index, I'm getting Lock obtain timed out.
It's in org.apache.lucene.store.Lock.obtain(Lock.java:58), which the user
list has referred
, it yields the following:
java.io.IOException: Lock obtain timed out:
Lock@/var/tmp/lucene-d6b0a3281487d1bc4d169d00426f475d-write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:58)
Now, this is on only two messages to the MDB, not just a flood of
messages. Two handlers, so I expect
with create=false
} catch (file not found) {
open the index with create=true
}
index.optimize();
index.close();
Now, when I fire off any messages to the MDB, it yields the following:
java.io.IOException: Lock obtain timed out:
Lock@/var/tmp/lucene-d6b0a3281487d1bc4d169d00426f475d-write.lock
the following:
java.io.IOException: Lock obtain timed out:
Lock@/var/tmp/lucene-d6b0a3281487d1bc4d169d00426f475d-write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:58)
Now, this is on only two messages to the MDB, not just a flood of
messages. Two handlers, so I expect
On Jan 6, 2005, at 10:41 AM, Joseph Ottinger wrote:
SHouldn't Lucene warn the user if they do something like this?
When a user indexes a null? Or attempts to write to the index from two
different IndexWriter instances?
I believe you should get an NPE if you try index a null field value?
No?
On Thu, 6 Jan 2005, Erik Hatcher wrote:
On Jan 6, 2005, at 10:41 AM, Joseph Ottinger wrote:
SHouldn't Lucene warn the user if they do something like this?
When a user indexes a null? Or attempts to write to the index from two
different IndexWriter instances?
I believe you should get an
(url, url));
IndexReader.open(dstDir).close();
-
The writer after that throws an IOException : Lock obtain timed out.
-
Analyzer analyzer = new StandardAnalyzer
.
-
int deleteDoc = 0;
deleteDoc = IndexReader.open(dstDir).delete(new Term(url, url));
IndexReader.open(dstDir).close();
-
The writer after that throws an IOException : Lock obtain timed out
I've noticed this really strange problem on one of our boxes. It's
happened twice already.
We have indexes where when Lucnes starts it says 'Lock obtain timed out'
... however NO locks exist for the directory.
There are no other processes present and no locks in the index dir or /tmp
To: Lucene Users List
Subject: 'Lock obtain timed out' even though NO locks exist...
I've noticed this really strange problem on one of our boxes. It's
happened twice already.
We have indexes where when Lucnes starts it says 'Lock obtain timed out'
... however NO locks exist for the directory
--- Kevin A. Burton [EMAIL PROTECTED] wrote:
I've noticed this really strange problem on one of
our boxes. It's
happened twice already.
We have indexes where when Lucnes starts it says
'Lock obtain timed out'
... however NO locks exist for the directory.
There are no other processes
[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
to open this index with Lock obtain timed out.
If I open it up from the console it works just fine. I'm only doing it
with one index and a ulimit -n so it's not a files issue. Memory is 1G
for Tomcat.
If I figure this out will be sure to send a message to the list. This
is a strange one
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
: '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 have a script that removes the locks from both
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
());
reader.close();
I put the first of the two lines in to try to force
the lock to disable. According to the logging, this
code is being called and the IndexReader is being
closed.
However, then I open a writer to add the document, I
get the following.
java.io.IOException: Lock obtain timed out
, then I open a writer to add the document, I
get the following.
java.io.IOException: Lock obtain timed out
at
org.apache.lucene.store.Lock.obtain(Lock.java:97)
at
org.apache.lucene.index.IndexWriter.init(IndexWriter.java:173)
at
...
I open the writer by calling
get the following.
java.io.IOException: Lock obtain timed out
at
org.apache.lucene.store.Lock.obtain(Lock.java:97)
at
org.apache.lucene.index.IndexWriter.init(IndexWriter.java:173)
at
...
I open the writer by calling:
return new IndexWriter
Did you close your writer if an Exception occured?
I had a similiar problem, but it was fixed when i close the writer in the
finally block.
Below is my original code (which generate Mjava.io.Exception: Lock obtain
timed out when an Exception is thrown)
public static void index(File indexDir
Mjava.io.Exception: Lock obtain
timed out when an Exception is thrown)
public static void index(File indexDir, List cList,
boolean ow)
throws Exception{
IndexWriter writer = null;
try{
writer = new IndexWriter(indexDir, new
MyAnalyzer(), overwrite);
// index documents
Mjava.io.Exception: Lock obtain
timed out when an Exception is thrown)
public static void index(File indexDir, List cList,
boolean ow)
throws Exception{
IndexWriter writer = null;
try{
writer = new IndexWriter(indexDir, new
MyAnalyzer(), overwrite);
// index
-Original Message-
From: Tatu Saloranta [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 7:23 AM
To: Lucene Users List
Subject: Re: Lock obtain timed out
On Tuesday 16 December 2003 03:37, Hohwiller, Joerg wrote:
Hi there,
I have not yet got any response about my
I am using Lucene final.if i want to delete the documents from the index with
IndexReader.delete(i) where i is doc. number in index.There will some problem occer
during obtaining of lock as file could not create in obtain() method of
FSDirectory.java
and following error occur: Lock obtain
Hi there,
I have not yet got any response about my problem.
While debugging into the depth of lucene (really hard to read deep insde) I
discovered that it is possible to disable the Locks using a System property.
When I start my application with -DdisableLuceneLocks=true,
I do not get the
16 décembre 2003 11:37
À : [EMAIL PROTECTED]
Objet : Lock obtain timed out
Hi there,
I have not yet got any response about my problem.
While debugging into the depth of lucene (really hard to read deep insde) I
discovered that it is possible to disable the Locks using a System property.
When I
Hohwiller, Joerg writes:
Am I safe disabling the locking???
No.
Can anybody tell me where to get documentation about the Locking
strategy (I still would like to know why I have that problem) ???
I guess -- but given your input I really have to guess; the source you
wanted to attach didn't
it at anytime?
David
-Original Message-
From: Morus Walter [mailto:[EMAIL PROTECTED]
Sent: 16 December 2003 11:08
To: Lucene Users List
Subject: Re: Lock obtain timed out
Hohwiller, Joerg writes:
Am I safe disabling the locking???
No.
Can anybody tell me where to get documentation
Hi there,
thanks for your resonse guys!
For the answers I got the info that I must not have an IndexWriter
and an IndexReader open at the same time that both want to modify
the index - even sequentially.
What I have is the following:
1 Thread is working out events such as resource (file or
On Tuesday 16 December 2003 03:37, Hohwiller, Joerg wrote:
Hi there,
I have not yet got any response about my problem.
While debugging into the depth of lucene (really hard to read deep insde) I
discovered that it is possible to disable the Locks using a System
property.
...
Am I safe
the index by a special field (in my case the URI), I get a IOException with the
message Lock obtain timed out.
I tried lucene 1.3-rc1, 1.3-rc2 and 1.3-rc3 all with the same result.
Any suggestions would be very welcome :)
Thank you so far
Jörg Hohwiller
BTW: I attatched the relevant source
31 matches
Mail list logo
