jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "RepositoryLock" by ThomasMueller
Date Thu, 10 Dec 2009 12:57:26 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "RepositoryLock" page has been changed by ThomasMueller.
http://wiki.apache.org/jackrabbit/RepositoryLock?action=diff&rev1=2&rev2=3

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

  == Repository Locking ==
+ 
+ <<TableOfContents>>
+ 
+ == Overview ==
  
  The repository lock mechanism ensures that only one Jackrabbit instance can open the same
repository at one time. By default, when a repository is started, Jackrabbit tries to create
a file named .lock in the repository home directory and protects it using using a native file
lock. If the repository is already in use, this will fail, usually with one of the following
exceptions / entries in the log file:
  
@@ -17, +21 @@

  In the first case, the repository is already open in another process. Please stop the other
process first.
  
  In the second and third case, the repository is already open in the same process but within
another class loader (for example, in another web application). In this case you need to ensure
that the repository is closed when the web-application is stopped.
+ 
+ == When To Delete the Lock File == 
+ 
+ Deleting the lock file manually is normally not necessary, even if the repository was not
closed before. 
+ 
+ The only case where it may be required to manually delete the repository lock file is when
using an NFS share (for some NFS implementations), and the NFS server died and was re-started.
Some NFS servers will not release the file lock in this case.
  
  == Using the Cooperative File Lock Mechanism ==
  

Mime
View raw message