此内容没有您所选择的语言版本。

4.3.2. Configure Local Mode (Remote Client-Server Mode)


A local cache can be added to any cache container. For example:
<cache-container name="local" 
		 default-cache="default" >
	<local-cache name="default" 
		     start="EAGER">
		<locking isolation="NONE" 
			 acquire-timeout="30000"
			 concurrency-level="1000" 
			 striping="false" />
		<transaction mode="NONE" />
	</local-cache>
</cache-container>
Alternatively, create a DefaultCacheManager with the "no-argument" constructor. Both of these methods create a local default cache.
Local and clustered caches are able to coexist in the same cache container, however where the container is without a <transport/> it can only contain local caches. The container used in the example can only contain local caches as it does not have a <transport/>.
The cache interface extends the ConcurrentMap and is compatible with multiple cache systems.
The local-cache Element

The local-cache element specifies information about the local cache used with the cache container using the following parameters:

  • The name parameter specifies the name of the local cache to use.
  • The start parameter indicates where the cache starts, i.e. whether it will start lazily when requested or when the server starts up. Valid values for this parameter are EAGER and LAZY.
  • The batching parameter specifies whether batching is enabled for the local cache.
  • The indexing parameter specifies the type of indexing used for the local cache. Valid values for this parameter are NONE, LOCAL and ALL.
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部