Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 40006 invoked from network); 14 Feb 2002 17:21:36 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Feb 2002 17:21:36 -0000 Received: (qmail 25458 invoked by uid 97); 14 Feb 2002 17:21:31 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@jakarta.apache.org Received: (qmail 25396 invoked by uid 97); 14 Feb 2002 17:21:30 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 25331 invoked from network); 14 Feb 2002 17:21:30 -0000 Message-ID: <4BC270C6AB8AD411AD0B00B0D0493DF001AC408F@mail.grandcentral.com> From: Doug Cutting To: 'Lucene Users List' , "'suneethad@india.adventnet.com'" Subject: RE: write.lock file Date: Thu, 14 Feb 2002 09:16:48 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I cannot replicate the problem you are having. Can you please submit a complete, self-contained, test case illustrating the problem you are having with the write lock. Please test this against the latest nightly build of Lucene, from: http://jakarta.apache.org/builds/jakarta-lucene/nightly/ Thanks, Doug -- To unsubscribe, e-mail: For additional commands, e-mail: