Yes - this 1.4 bug is what induced us to upgrade to 1.9! So, finding the same
problem in a different guise in 1.9 is quite an unfortunate coincidence!
-----Original Message-----
From: Daniel Naber [mailto:[EMAIL PROTECTED]
Sent: 14 March 2006 19:38
To: java-user@lucene.apache.org
Subject: Re: Setting the COMMIT lock timeout.
On Dienstag 14 März 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
another bug in 1.4 that made the default timeout not work. From the
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
--
http://www.danielnaber.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
