Enumerates the cache containers available to the registry. Defines an embedded cache container. Defines a remote cache container. Overrides the transport characteristics for this cache container. Defines a thread pool used for asynchronous operations. Defines a thread pool used for asynchronous cache listener notifications. Defines a thread pool used to execute remote commands. Defines a thread pool used for for state transfer. Defines a thread pool used for asynchronous transport communication. Defines a scheduled thread pool used for expiration. Defines a thread pool used for interacting with the persistent store. Defines a local mode cache. Defines a replication mode cache. Defines an invalidation mode cache. Defines a distribution mode cache. Defines a scattered mode cache. Uniquely identifies this cache container. A set of aliases by which this cache container may also be referenced. Indicates the default cache for this cache container. Defines the module whose class loader should be used when building this cache container. Determines whether or not the cache container should collect statistics. Keep disabled for optimal performance. Defines the channel used for this transport. Defines the jgroups stack used by the transport. Infinispan uses a distributed lock to maintain a coherent transaction log during state transfer or rehashing, which means that only one cache can be doing state transfer or rehashing at the same time. This constraint is in place because more than one cache could be involved in a transaction. This timeout controls the time to wait to acquire acquire a lock on the distributed lock. The locking configuration of the cache. The cache transaction configuration. The cache memory configuration. The cache memory configuration. The cache memory configuration. The cache expiration configuration. Defines a custom cache store. Defines a file-based cache store. Defines a database cache store accessed via JDBC using string-based keys. Defines a database cache store accessed via JDBC using binary-based keys. Warning: This option has been deprecated, please use jdbc-store instead Defines a database cache store accessed via JDBC using mixed string and binary-based keys. Warning: This option has been deprecated, please use jdbc-store instead. Defines a remote cache store accessed via HotRod. Nested properties will be treated as HotRod client properties. HotRod-based store using Infinispan Server instance to store data. Uniquely identifies this cache within its cache container. Defines the module whose class loader should be used when building this cache, if different from the enclosing cache container. Determines whether or not the cache should collect statistics. Keep disabled for optimal performance. Sets the cache locking isolation level. If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system. Maximum time to attempt a particular lock acquisition. Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan. Defines the transaction mode of the cache. If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout. The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC. Maximum size of this cache. Sets the cache eviction type. Capability of the off-heap storage. Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire. Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire. Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1. In SYNC mode, the timeout (in ms) used to wait for an acknowledgment when making a remote call, after which the call is aborted and an exception is thrown. The partition handling configuration for distributed and replicated caches. The state transfer configuration for distributed and replicated caches. A list of backup sites for this cache (for use with cross-site replication). Number of hash space segments (per cluster). Defines the consistent hash strategy for the cache. This determines the consistent hash factory to use for generating the consistent hash. Number of cluster-wide replicas for each cache entry. Maximum lifespan in milliseconds of an entry placed in the L1 cache. Controls the proportion of entries that will reside on the local node, compared to the other nodes in the cluster. When greater than zero, specifies the duration (in ms) that a cache entry will be cached on a non-owner following a write operation. The threshold after which batched invalidations are sent. Configures a cache store as write-behind instead of write-through. A cache store property with name and value. The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch. 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. 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. 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. f 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. If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled. If true, purges this cache store when it starts up. 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. Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through. until it can accept new entries Size of the thread pool whose threads are responsible for applying the modifications to the cache store. The class name of the cache store implementation. The base directory in which to store the cache state. The path within "relative-to" in which to store the cache state. If undefined, the path defaults to the cache container name. A list of outbound socket bindings. The name of the remote cache. If undefined, the default cache will be used. Enable/disable SO_TIMEOUT on socket connections to remote Hot Rod servers with the specified timeout, in milliseconds. A timeout of zero is interpreted as an infinite timeout. Enable/disable TCP_NODELAY on socket connections to remote Hot Rod servers. Name of the cache configuration template defined in Infinispan Server to create caches from. Reference to a container-managed remote-cache-container. References the pool name of a data source. Defines the JDBC dialect. Defines the table used to store cache entries. Defines the table used to store cache buckets. Defines the table used to store cache buckets. Defines the table used to store cache entries. Defines the prefix prepended to the cache name used when composing the name of the cache entry table. Defines the prefix prepended to the cache name used when composing the name of the cache bucket table. Defines the column in which to store the cache key or bucket id. Defines the column in which to store the cache entry or bucket. Defines the column in which to store the timestamp of the cache entry or bucket. The fetch size used when querying from this table. Used to avoid heap memory exhaustion when query is large. Indicates whether the store should create this database table when the cache starts. Indicates whether the store should drop this database table when the cache stops. The name of the column used to store the cache key or bucket id. The type of the column used to store the cache key or bucket id. The name of the column used to store the cache entry or bucket. The type of the column used to store the cache entry or bucket. The name of the column used to store the cache entry or bucket timestamp. The type of the column used to store the cache entry or bucket timestamp. If enabled, the cache will enter degraded mode upon detecting a network partition that threatens the integrity of the cache. The maximum amount of time (in ms) to wait for state from neighboring caches, before throwing an exception and aborting startup. A timeout of 0 means the cache will be available immediately after joining, and initial state transfer is non-blocking. The number of cache entries to batch in each transfer. A backup site for this cache. Control when to take this backup site offline. The name of this remote site. The backup strategy for this cache. The policy to follow when connectivity to the backup site fails. The timeout for replicating to the backup site. Indicates whether or not this backup site is enabled. The name of the remote cache for which this cache acts as a backup The site of the remote cache for which this cache acts as a backup. Indicates the number of failures after which this backup site should go offline. Indicates the minimum time (in milliseconds) to wait after the max number of failures is reached, after which this backup site should go offline. Defines the name of a property. No locking isolation will be performed. This is only valid in local mode. In clustered mode, READ_COMMITTED will be used instead. Unsupported. Actually configures READ_COMMITTED. Read committed is an isolation level that guarantees that any data read is committed at the moment it is read. However, depending on the outcome of other transactions, successive reads may return different results. Repeatable read is an isolation level that guarantees that any data read is committed at the moment it is read and that, within a transaction, successive reads will always return the same data. Unsupported. Actually configures REPEATABLE_READ. Cache will be non-transactional. Cache will support batching of operations. Cache will enlist within transactions as a javax.transaction.Synchronization Cache will enlist within transactions as a javax.transaction.xa.XAResource, without recovery. Cache will enlist within transactions as a javax.transaction.xa.XAResource, with recovery. Evicts the oldest entries when the number of cache entries exceeds the specified size. Evicts the oldest entries when the total memory size of cache entries exceeds the specified size. Enables asynchronous mode. Enables synchronous mode. Enables Optimistic locking. Enables Pessimistic locking. Ignore backup failures. Warn of backup failures. Fail local operations when a backup failure occurs. A given cache key will have the same consistent hash on every node on any cache with the same topology. A given cache key will have the same consistent hash on every node within a given cache with the same topology. Minimum thread pool size for the thread pool. Maximum thread pool size for the thread pool. Maximum queue length for the thread pool. Timeout in milliseconds to remove idle thread from the pool. Fixed thread pool size for the scheduled thread pool. Timeout in milliseconds to remove idle thread from the scheduled thread pool. Configuration for the executor service used for asynchronous work on the Transport, including asynchronous marshalling and Cache async operations such as RemoteCache.putAsync(). Configuration of the connection pool. Configures using near cache in invalidated mode. When entries are updated or removed server-side, invalidation messages will be sent to clients to remove them from the near cache. A property with name and value. Configures remote server clusters for Hot Rod client to connect to. Security configuration. Transaction configuration. Defines the maximum socket connect timeout before giving up connecting to the server. Specifies the default remote server cluster. This hint allows sizing of byte buffers when serializing and deserializing keys, to minimize array resizing. Sets the maximum number of retries for each request. A valid value should be greater or equals than 0. Value of 0 means no retry will made in case of a network failure. Defines the module whose class loader should be used when configuring remote cache container marshaller. Uniquely identifies this remote cache container. Defines the protocol version that this client should use. Enable or disable SO_TIMEOUT on socket connections to remote Hot Rod servers with the specified timeout, in milliseconds. A timeout of 0 is interpreted as an infinite timeout. Enables statistics gathering for this remote cache. Enable or disable TCP_NODELAY on socket connections to remote Hot Rod servers. Configures TCP keepalive on the TCP stack. This hint allows sizing of byte buffers when serializing and deserializing values, to minimize array resizing. Defines remote server cluster. Name of remote server cluster. List of socket bindings of remote servers. Defines the maximum number of elements to keep in the near cache. Specifies what happens when asking for a connection from a server's pool, and that pool is exhausted. Controls the maximum number of connections per server that are allocated (checked out to client threads, or idle in the pool) at one time. When non-positive, there is no limit to the number of connections per server. When maxActive is reached, the connection pool for that server is said to be exhausted. Value -1 means no limit. The amount of time in milliseconds to wait for a connection to become available when the exhausted action is ExhaustedAction.WAIT, after which a java.util.NoSuchElementException will be thrown. If a negative value is supplied, the pool will block indefinitely. Specifies the minimum amount of time that an connection may sit idle in the pool before it is eligible for eviction due to idle time. When non-positive, no connection will be dropped from the pool due to idle time alone. This setting has no effect unless timeBetweenEvictionRunsMillis > 0. Sets a target value for the minimum number of idle connections (per server) that should always be available. If this parameter is set to a positive number and timeBetweenEvictionRunsMillis > 0, each time the idle connection eviction thread runs, it will try to create enough idle instances so that there will be minIdle idle instances available for each server. An exception will be thrown to the calling user. The caller will block by invoking waits until a new or idle connections is available. A new persistent connection will be created and returned thus rendering maxActive meaningless. Reference to the Elytron-managed SSLContext to be used for connecting to the remote cluster. Reference to the Elytron-managed SSLContext to be used for connecting to the remote cluster. The duration (in ms) after which idle transactions are rolled back. Cache will be non-transactional. Cache will support batching of operations. Cache will enlist within transactions as a javax.transaction.xa.XAResource, without recovery.