1.24.2.2. Simple JbossCache Configuration

The first one is putting JbossCache configuraion file path to CacheableLockManagerImpl.

Note

This configuration is not so good as you think. Because the repository may contain many workspaces, and each workspace must contain LockManager configuration, and LockManager configuration may contain the JbossCache config file. So, the total configuration will grow up. But it is useful if we want to have a single LockManager with a special configuration.

Configuration is as follows:


<lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl">

   <properties>

     <property name="time-out" value="15m" />

     <property name="jbosscache-configuration" value="conf/standalone/cluster/test-jbosscache-lock-config.xml" />

   </properties>

</lock-manager>

test-jbosscache-lock-config.xml


<?xml version="1.0" encoding="UTF-8"?>

<jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.2">



 <locking useLockStriping="false" concurrencyLevel="500" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000" />



 <clustering mode="replication" clusterName="JBoss-Cache-Lock-Cluster_Name">

  <stateRetrieval timeout="20000" fetchInMemoryState="false" />

  <sync />

 </clustering>



 <loaders passivation="false" shared="true">

  <preload>

   <node fqn="/" />

  </preload>

  <loader class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.JDBCCacheLoader" async="false" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">

   <properties>

    cache.jdbc.table.name=jcrlocks_ws

    cache.jdbc.table.create=true

    cache.jdbc.table.drop=false

    cache.jdbc.table.primarykey=jcrlocks_ws_pk

    cache.jdbc.fqn.column=fqn

    cache.jdbc.fqn.type=VARCHAR(512)

    cache.jdbc.node.column=node

    cache.jdbc.node.type=<BLOB>  

    cache.jdbc.parent.column=parent

    cache.jdbc.datasource=jdbcjcr

   </properties>

  </loader>



 </loaders>



</jbosscache>

Configuration requirements:

<clustering mode="replication" clusterName="JBoss-Cache-Lock-Cluster_Name"> - the cluster name must be unique;
cache.jdbc.table.name must be unique per datasource;
cache.jdbc.node.type and cache.jdbc.fqn.type must be configured according to your database.
Note
To prevent any consistency issue regarding the lock data please ensure that your cache loader is org.exoplatform.services.jcr.impl.core.lock.jbosscache.JDBCCacheLoader and that your database engine is transactional.