Mailing-List: contact java-commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Wed, 20 Jan 2010 13:29:13 -0000
Message-ID: <20100120132913.445.88723@eos.apache.org>
Subject: 
 =?utf-8?q?=5BLucene-java_Wiki=5D_Update_of_=22AvailableLockFactories=22_b?=
 =?utf-8?q?y_SanneGrinovero?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" f=
or change notification.

The "AvailableLockFactories" page has been changed by SanneGrinovero.
http://wiki.apache.org/lucene-java/AvailableLockFactories?action=3Ddiff&rev=
1=3D3&rev2=3D4

--------------------------------------------------

  =

  Qualified Class``Name: {{{org.apache.lucene.store.NativeFSLockFactory}}}
  =

- This implementation is similar to Simple``F``S``Lock``Factory, they both =
extend F``S``Lock``Factory and rely on a lock file. This version relies on =
N``I``O and the lock files will be properly removed (by the OS) if the JVM =
has an abnormal exit, but should be avoided on N``F``S: make sure you read =
the javadocs for updated details.
+ This implementation is similar to Simple``F``S``Lock``Factory, they both =
extend F``S``Lock``Factory and rely on a lock file. This version relies on =
N``I``O and the lock files will be properly removed (by the O``S) if the J`=
`V``M has an abnormal exit, but should be avoided on N``F``S: make sure you=
 read the javadocs for updated details.
+ Because the lock is obtained for the current process different applicatio=
ns in the same J``V``M might not be excluded properly; Lucene makes an atte=
mpt to prevent this issue using a static reference to owned locks, but when=
 loaded in an isolated classloader or when reloading the same web applicati=
on this workaround is not effective.
  =

  ----
 =20