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 "Clustering" by ThomasMueller
Date Thu, 03 Feb 2011 12:57:17 GMT
Dear Wiki user,

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

The "Clustering" page has been changed by ThomasMueller.


  All cluster nodes must point to the same persistence location. For performance reasons,
only information identifying the modified items is stored in the journal. This implies, that
all cluster nodes must configure the same persistence manager and persistence location, because
they must have access to the items' actual content. The persistence manager needs to be transactional,
and need to support concurrent access from multiple processes. When using Jackrabbit, one
option is to use a database persistence manager, and use a database that does support concurrent
access. The file system based persistence managers in Jackrabbit are not transactional and
don't support concurrent access; Apache Derby doesn't support concurrent access in the embedded
mode. The following sample shows a workspace's persistence manager configuration using an
Oracle database:
- <PersistenceManager class="org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager">
+ <PersistenceManager class="org.apache.jackrabbit.core.persistence.pool.OraclePersistenceManager">
    <param name="url" value="jdbc:oracle:thin:@myhost:1521:mydb" />
    <param name="user" value="scott"/>
    <param name="password" value="tiger"/>
    <param name="schemaObjectPrefix" value="${wsp.name}_"/>
-   <param name="externalBLOBs" value="false"/>
+ Previous versions of Jackrabbit that do not support this persistence manager may need to
use org.apache.jackrabbit.core.persistence.db.!OraclePersistenceManager.
  === Data Store Configuration ===

View raw message