Name Type Default Description
relative-to string jboss.server.data.dir The base directory in which to store the cache state.
path string The path within "relative-to" in which to store the cache state. If undefined, the path defaults to the cache container name.
block-size integer Cache store block size.
cache-size long Cache size for the cache store.
clear-threshold integer Cache store cache clear threshold.


Defines the expiration settings for the LevelDB cache store.

Name Type Default Description
path string The base directory in which to store expired cache state.
queue-size integer 10000 Expired entry queue size.


Defines the LevelDB store implementation to use.

Name Type Default Description
AUTO LevelDB implementation selection left to the library.
JAVA Selects LevelDB Java implementation.
JNI Selects LevelDB JNI implementation.
AUTO The LevelDB store implementation to use.


Defines the data compression to use in the LevelDB store.

Name Type Default Description
NONE No compression.
SNAPPY Snappy compression.
NONE The type of compression to be used by LevelDB store.
Name Type Default Description
name string Unused XML attribute
shared boolean false This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
preload boolean false If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
passivation boolean true If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
fetch-state boolean true If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
purge boolean true If true, purges this cache store when it starts up.
singleton boolean false If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
read-only boolean false If true, the cache store will only be used to load entries. Any modifications made to the caches will not be applied to the store.


Configures a cache store as write-behind instead of write-through.

Name Type Default Description
flush-lock-timeout int 1 Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
modification-queue-size int 1024 Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through. until it can accept new entries
shutdown-timeout int 25000 Timeout in milliseconds to stop the cache store.
thread-pool-size int 1 Size of the thread pool whose threads are responsible for applying the modifications to the cache store.


A cache store property with name and value.

Expand/Collapse All