8.3. Configure Replication Mode (Remote Client-Server Mode)

Procedure 8.1. The replicated-cache Element

<cache-container name="clustered" 
		 default-cache="default" 
		 statistics="true">
        <transport executor="infinispan-transport" 
        	   lock-timeout="60000"/>
	<replicated-cache name="default" 
				mode="SYNC"
				start="EAGER"
				statistics="true">
		<transaction mode="NONE" />
	</replicated-cache>
</cache-container>

<cache-container name="clustered" 
		 default-cache="default" 
		 statistics="true">
        <transport executor="infinispan-transport" 
        	   lock-timeout="60000"/>
	<replicated-cache name="default" 
				mode="SYNC"
				start="EAGER"
				statistics="true">
		<transaction mode="NONE" />
	</replicated-cache>
</cache-container>

1. The name parameter provides a unique identifier for the cache.
2. The mode parameter sets the clustered cache mode. Valid values are SYNC (synchronous) and ASYNC (asynchronous).
3. The start parameter specifies whether the cache starts when the server starts up or when it is requested or deployed.
4. If statistics are enabled at the container level, per-cache statistics can be selectively disabled for caches that do not require monitoring by setting the statistics attribute to false.
5. The transaction element sets up the transaction mode for the replicated cache.

   Important

   In Remote Client-Server mode, the transactions element is set to NONE unless JBoss Data Grid is used in a compatibility mode where the cluster contains both JBoss Data Grid server and library instances. In this case, if transactions are configured in the library mode instance, they must also be configured in the server instance.