[CAMEL-19096] EhcacheAggregationRepository drops messages on OversizeMappingException

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Information Provided
• Affects Version/s: 3.14.7
• Component/s: camel-ehcache
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Pieter Callewaert
• Created: 27/Feb/23 16:15
• Updated: 28/Mar/23 05:31
• Resolved: 28/Mar/23 05:31

Description

When using an EhCacheAggregationRepository with an offheap store and the aggregated exchange becomes too large, the cache entry is cleared, effectively loosing exchanges.

Have a route that aggregates string message bodies by aggregating them by concatinating the messages.  The aggregation is completed per 100 messages or 5 minutes. The aggregationRepository has a disk backed store.

When the aggregated exchange becomes to large, EhCache throws an 

 o.e.i.i.r.RobustResilienceStrategy - Ehcache key true recovered from
org.ehcache.spi.resilience.StoreAccessException: The element with key 'true' is too large to be stored in this offheap store.
        at org.ehcache.impl.internal.store.offheap.AbstractOffHeapStore.computeWithRetry(AbstractOffHeapStore.java:1038)        at org.ehcache.impl.internal.store.offheap.AbstractOffHeapStore.put(AbstractOffHeapStore.java:250)
        at org.ehcache.impl.internal.store.tiering.TieredStore.put(TieredStore.java:108) 

after this call the entry in the cache is removed, effectively loosing messages.

        cacheManager.createCache("cacheName", CacheConfigurationBuilder
                .newCacheConfigurationBuilder(String.class, DefaultExchangeHolder.class,
                        ResourcePoolsBuilder.newResourcePoolsBuilder()
                                .heap(1000, EntryUnit.ENTRIES)
                                .disk(1, MemoryUnit.MB, true))
                .withExpiry(ExpiryPolicyBuilder.noExpiration()));

Attached is a project demonstrating the behaviour. As a reference there is also a variant with LevelDb which behaves as expected.