| Name | Type | Default | Description |
|---|---|---|---|
| location | string | Infinispan-BdbjeCacheStore | Location on disk where the store can write internal files. |
| lockAcquistionTimeout | int | 60000 | The length of time, in milliseconds, to wait for locks before timing out and throwing an exception. By default, this is set to 60000 |
| maxTxRetries | int | 5 | The number of times transaction prepares will attempt to resolve a deadlock before throwing an exception. By default, this is set to 5 |
| cacheDbNamePrefix | string | The name of the SleepyCat database persisting this store. This defaults to {cache_name} | |
| catalogDbName | string | The name of the SleepyCat database persisting the class information for objects in this store. This defaults to {cache_name}_class_catalog | |
| expiryDbPrefix | string | The prefix of the SleepyCat database persisting the expiration data for objects in this store. If unset the name of the database will be {cache_name}_expiry | |
| environmentPropertiesFile | string | The name of the SleepyCat properties file containing je.* properties to initialize the JE environment. Defaults to null, no properties are passed in to the JE engine if this is null or empty. The file specified needs to be available on the classpath, or must be an absolute path to a valid properties file. Refer to SleepyCat JE Environment configuration documentation for details. |
| Name | Type | Default | Description |
|---|---|---|---|
| fetchPersistentState | boolean | false | If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled. Persistent state transfer with a shared cache store does not make sense, as the same persistent store that provides the data will just end up receiving it. Therefore, if a shared cache store is used, the cache will not allow a persistent state transfer even if a cache store has this property set to true. Finally, setting it to true only makes sense if in a clustered environment, and only 'replication' and 'invalidation' cluster modes are supported. Defaults to false. |
| ignoreModifications | boolean | false | If true, any operation that modifies the cache (put, remove, clear, store...etc) won't be applied to the cache store. This means that the cache store could become out of sync with the cache. Defaults to false. |
| purgeOnStartup | boolean | false | If true, purges this cache store when it starts up. Defaults to false. |
| purgeSynchronously | boolean | false | If true, CacheStore#purgeExpired() call will be done synchronously. Defaults to false. |
| purgerThreads | int | 1 | The number of threads to use when purging asynchronously. Defaults to 1 thread. |
async?
Configuration for the async cache loader. If enabled, this provides you with asynchronous writes to the cache store, giving you 'write-behind' caching.
| Name | Type | Default | Description |
|---|---|---|---|
| enabled | boolean | false | If true, all modifications to this cache store happen asynchronously, on a separate thread. |
| flushLockTimeout | long | 1 | Timeout to acquire the lock which guards the state to be flushed to the cache store periodically. Defaults to 1. |
| modificationQueueSize | int | 1024 | Sets the size of the modification queue for the async store. If updates are made at a rate that is faster than the underlying cache store can process this queue, then the async store behaves like a synchronous store for that period, blocking until the queue can accept more elements. Defaults to 1024 elements. |
| shutdownTimeout | long | 25000 | Timeout to stop the cache store. When the store is stopped it's possible that some modifications still need to be applied; you likely want to set a very large timeout to make sure to not loose data. Defaults to 25 seconds. |
| threadPoolSize | int | 1 | Size of the thread pool whose threads are responsible for applying the modifications. Defaults to 1. |
singletonStore?
SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store. The coordinator of the cluster will be responsible for the underlying CacheStore. SingletonStore is a simply facade to a real CacheStore implementation. It always delegates reads to the real CacheStore.
| Name | Type | Default | Description |
|---|---|---|---|
| pushStateTimeout | long | 10000 | If pushStateWhenCoordinator is true, this property sets the maximum number of milliseconds that the process of pushing the in-memory state to the underlying cache loader should take. Defaults to 10 seconds. |
| pushStateWhenCoordinator | boolean | true | If true, when a node becomes the coordinator, it will transfer in-memory state to the underlying cache store. This can be very useful in situations where the coordinator crashes and there's a gap in time until the new coordinator is elected. Defaults to true. |
| enabled | boolean | false | If true, the singleton store cache store is enabled. Defaults to false. |
properties?
Properties passed to the cache store or loader
property*
| Name | Type | Default | Description |
|---|---|---|---|
| name | string | The property name or key | |
| value | string | The property value |