Thanks for your prompt response! You ask about the use case. We have a series of similar intranet sites, each represented by a separate tomcat application instance using the same code base but with different start-up parameters. The intranets all provide a common search function based on the same underlying index.
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. -----Original Message----- From: Daniel Naber [mailto:[EMAIL PROTECTED] Sent: 13 March 2006 23:23 To: java-user@lucene.apache.org Subject: Re: Setting the COMMIT lock timeout. On Montag 13 März 2006 22:24, Bill Janssen wrote: > The default value isn't magic. The appropriate value is > context-specific. I've got some people using Lucene on machines with > slow disks, and we need to be able to increase the WRITE_LOCK_TIMEOUT > to prevent entirely random lossage. Here's a patch (I hope it gets through). Let me know if it's okay, I will commit it then. Regards Daniel -- http://www.danielnaber.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
