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 Mon, 04 Jan 2010 11:17:17 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=3&rev2=4

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

  
  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.
  
+ == Why Is the Repository Locked ==
+ 
+ Jackrabbit works like a file system or database: to improve performance, Jackrabbit caches
frequently used data, and keeps transient changes in memory until they are saved explicitly.
Therefore, to avoid inconsistencies and corruption, it must be ensured that the same repository
is only accessed by one process at a time.
+ 
+ == How to Access the Repository from Multiple Processes ==
+ 
+ Jackrabbit supports multiple [[http://jackrabbit.apache.org/deployment-models.html|Deployment
Models]]. To access the same repository from multiple computers or processes, use a [[http://jackrabbit.apache.org/repository-server-howto.html|Repository
Server]].
+ 
+ An alternative to using to use [[Clustering]].
+ 
- == When To Delete the Lock File == 
+ == When to Manually Delete the Lock File ==
  
  Deleting the lock file manually is normally not necessary, even if the repository was not
closed before. 
  

Mime
View raw message