JBoss EAP 7.1 Model Reference

  1. JBoss EAP 7.1
  2. subsystem=infinispan
  3. cache-container
  4. distributed-cache
  5. component=expiration

The cache expiration configuration.

Attributes (3)

  • interval 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.
    • Attribute Value
    Default Value 60000
    Type LONG
    Nillable true
    Expressions Allowed true
    Unit MILLISECONDS
    Storage configuration
    Access Type read-write
    Restart Required resource-services
  • lifespan Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
    • Attribute Value
    Default Value -1
    Type LONG
    Nillable true
    Expressions Allowed true
    Unit MILLISECONDS
    Storage configuration
    Access Type read-write
    Restart Required resource-services
  • max-idle 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.
    • Attribute Value
    Default Value -1
    Type LONG
    Nillable true
    Expressions Allowed true
    Unit MILLISECONDS
    Storage configuration
    Access Type read-write
    Restart Required resource-services

Operations (2)

  • add Adds an expiration configuration element to the cache.
    Request Parameter Type Required Expressions Allowed Default value Description
    interval LONG false true 60000 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.
    lifespan LONG false true -1 Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
    max-idle LONG false true -1 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.
  • remove Removes an expiration configuration element from the cache.