CODEWITHSUNDEEP
javaspringspring-bootehcachespring-cache
Oleg
Oleg

Reputation: 3014

EhCache - Expired elements won't evict

I'm using EHCache 2.9 in my Spring Boot application and I've configured the cache to expire after 300 seconds (5 minutes).

When I run the application and request the element for the first time it gets cached and after that never expires. However, when I do @CachePut it gets updated successfully and updated element is then returned. What is wrong in my configuration?

Here is my ehcache.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<ehcache>
    <defaultCache maxElementsInMemory="500" eternal="false"
                  overflowToDisk="false" memoryStoreEvictionPolicy="LFU" />

    <diskStore path="java.io.tempdir"/>

    <cache name="appointments"
           maxElementsInMemory="5000"
           eternal="false"
           timeToIdleSeconds="0"
           timeToLiveSeconds="300"
           overflowToDisk="false"
           memoryStoreEvictionPolicy="LFU" />

</ehcache>

And here is how I request the cache:

@Cacheable("appointments")
public List<Event> getEvents(String eventsForUser, Date startDate, Date endDate) throws Exception {

    return fetchEventsFromTheServer(eventsForUser, startDate, endDate);
}

@CachePut("appointments")
public List<Event> refreshEventsCache(String eventsForUser, Date startDate, Date endDate) throws Exception {

    return fetchEventsFromTheServer(eventsForUser, startDate, endDate);
}

Any suggestions?

Upvotes: 0

Views: 2945

Answers (1)

Marius Gaina Cristea
Marius Gaina Cristea

Reputation: 1

Flush – To move a cache entry to a lower tier. Flushing is used to free up resources while still keeping data in the cluster. Entry E1 is shown to be flushed from the L1 off-heap store to the Terracotta Server Array (TSA).

Fault – To copy a cache entry from a lower tier to a higher tier. Faulting occurs when data is required at a higher tier but is not resident there. The entry is not deleted from the lower tiers after being faulted. Entry E2 is shown to be faulted from the TSA to L1 heap.

Eviction – To remove a cache entry from the cluster. The entry is deleted; it can only be reloaded from a source outside the cluster. Entries are evicted to free up resources. Entry E3, which exists only on the L2 disk, is shown to be evicted from the cluster.

Expiration – A status based on Time To Live and Time To Idle settings. To maintain cache performance, expired entries may not be immediately flushed or evicted. Entry E4 is shown to be expired but still in the L1 heap.

Pinning – To force data to remain in certain tiers. Pinning can be set on individual entries or an entire cache, and must be used with caution to avoid exhausting a resource such as heap. E5 is shown pinned to L1 heap.

http://www.ehcache.org/documentation/2.7/configuration/data-life.html

Upvotes: -1

Related Questions