Check Ehcache configuration

When using Ehcache, some configuration elements can cause instability to your application if they are not configured properly.

This rule scans for configuration elements in the ehcache.xml file that are known to cause instability.

• maxElementsInMemory : This element is flagged because it does not cap the number of bytes in the cache. A single element can be 1 GB.
• maxEntriesLocalHeap : This element is flagged because it does not cap the size of the cache. A single entry can be 1 GB.
• timeToIdleSeconds and timeToLiveSeconds : These elements are flagged in the following cases.
  • When the value is 0 , which means it is never evicted from the cache
  • When the value is 3600 or greater, because this setting is very large

Instead of using the maxElementsInMemory or maxEntriesLocalHeap elements, consider using the maxBytesLocalHeap element in your Ehcache cache configuration to limit the heap usage. Evaluate these configuration settings to avoid stability issues such as out-of-memory errors or errors that occur during heavy loads.