Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of lucenelist2005@danielnaber.de
 designates 80.67.18.13 as permitted sender)
From: Daniel Naber <lucenelist2005@danielnaber.de>
To: java-user@lucene.apache.org
Subject: Re: Setting the COMMIT lock timeout.
Date: Tue, 14 Mar 2006 20:37:39 +0100
User-Agent: KMail/1.8.2
References: <40D92B748B99CC43A2F0897B6B2B822E0211DF53@ukex02.framfab.com>
In-Reply-To: <40D92B748B99CC43A2F0897B6B2B822E0211DF53@ukex02.framfab.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200603142037.39368@danielnaber.de>

On Dienstag 14 M=C3=A4rz 2006 10:52, Jim Bedford-roberts wrote:

> Admittedly we could have developed a single central search component,
> but given the way the code has evolved our current approach is simplest
> for us. With separate application instances sharing access to the same
> index we are getting occasional COMMIT lock time outs even while using
> singleton IndexSearchers in each application.

Have you already tried using Lucene 1.9 without my patch? Because there was=
=20
another bug in 1.4 that made the default timeout not work. From the=20
changelog:

7. Getting a lock file with Lock.obtain(long) was supposed to wait for
    a given amount of milliseconds, but this didn't work.
    (John Wang via Daniel Naber, Bug #33799)

Regards
 Daniel

=2D-=20
http://www.danielnaber.de

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org