Ehcache cache

Max entries local heap

Sets the maximum number of objects that will be created in the local JVM's heap memory. Value zero indicates no limit: in practice no limit means Integer.MAX_SIZE (2147483647).

This attribute and max bytes local heap are mutually exclusive.

If max bytes local heap is not specified on the cache manager level, this attribute or max bytes local heap, is required and cannot be a percentage.

Max bytes local heap

Constraints the memory usage of this cache to use at most the specified amount of the local JVM's heap. If the cache manager's max bytes local heap has been defined, this cache's specified amount will be subtracted from the cache manager memory pool. Other caches will share the remainder.

Can be specified as an absolute amount of memory, or as a percentage of the cache manager's max bytes local heap attribute.

Some examples: 25%, 1073741824B, 1048576K, 1024M, 1G

This attribute and max entries local heap are mutually exclusive.

If max bytes local heap is not specified on the cache manager level, this attribute or max entries local heap, is required and cannot be a percentage.

Memory store eviction policy

The policy used to evict elements from the heap memory upon reaching the specified limit.

This can be one of:

• LRU: least recently used (based on time of last access)
• LFU: less frequently used (based on number of accesses)
• FIFO: first in first out (based on time of creation)

If not filled it defaults to LRU.

Overflow to disk

Explicitly sets whether this Cache will overflow to disk when the in-memory cache has reached the specified limit.

If not specified, it will default to true if a disk pool is specified with the max bytes local disk attribute on the cache and/or cache manager level, or false otherwise.

Max entries local disk

Sets the maximum number of objects that will be stored on disk. Value zero indicates no limit: in practice no limit means Integer.MAX_SIZE (2147483647).

This property and max bytes local disk are mutually exclusive.

If max bytes local disk is specified on the cache manager level, this property cannot be used.

If not filled it defaults to 0.

Max bytes local disk

Constraints the disk usage of this cache to use at most the specified amount of the local disk. If the cacheManager's max bytes local disk attribute has been defined, this cache's specified amount will be subtracted from the cache manager disk pool. Other caches will share the remainder.

Can be specified as an absolute amount of disk space, or as a percentage of the cache manager's max bytes local disk attribute. Some examples: 25%, 1073741824B, 1048576K, 1024M, 1G

This property and max entries local disk are mutually exclusive.

If the max bytes local disk attribute is not specified on the cache manager level, this property cannot be a percentage.

Disk persistent

Determines whether to persist the cache to disk between JVM restarts. Note that this operates independently of overflow to disk.

If not specified, it will default to false.

Eternal

Sets whether cached elements are eternal. If eternal, timeouts are ignored and elements never expire.

Default is false.

Time to idle

Sets the time to idle for an element before it expires, i.e. the maximum amount of time in seconds between accesses before an element expires. Is only used if the element is not eternal.

If not filled it defaults to 0, which indicates that an element can idle for infinity.

Time to live

Sets the time to live for an element before it expires, i.e. the maximum amount of time in seconds between creation time and when an element expires. Is only used if the element is not eternal.

If not filled it defaults to 0, which indicates that an element can live for infinity.

Disk spool buffer size

The size (in MiB) to allocate the DiskStore for a spool buffer. Writes are made to this area and then asynchronously written to disk. Each spool buffer is used only by its cache. If you get OutOfMemory errors consider lowering this value. To improve DiskStore performance consider increasing it. Trace level logging in the DiskStore will show if put back ups are occurring.

If not filled it defaults to 30 MiB.

Disk access stripes

Sets the number of concurrent disk access stripes (RandomAccessFiles used to access the data file).

Default is 1.

Disk expiry thread interval

Sets the interval in seconds between runs of the disk expiry thread. This is not the same thing as time to live or time to idle. When the thread runs it checks these settings. So this value is how often we check for expiry.

If not filled it defaults to 120 seconds.

Name

The name of the cache.

Note: if you're using this cache for the eMagiz mapping service, the following named caches must exist:

• emagiz_mapping_cdmCodes
• emagiz_mapping_systemCodes
• emagiz_mapping_customAttributes

Required