Ehcache 4.3.7.Final配置问题：Hibernate二级缓存配置异常求助

First, let's lay out your current config clearly for reference:

<!-- Propiedades Cache Provider -->
<property name="hibernate.cache.provider_class">org.hibernate.cache.EhCacheProvider</property>
<property name="hibernate.cache.use_structured_entries">true</property>
<property name="hibernate.cache.use_query_cache">true</property>
<property name="hibernate.cache.use_second_level_cache">true</property>

Based on this setup, here are the most common pitfalls and fixes to check:

1. Missing or Mismatched Dependencies #

First off, make sure you’ve got the right EhCache dependencies in your project. The org.hibernate.cache.EhCacheProvider class is a legacy implementation from Hibernate 3.x. If you’re using Hibernate 4 or later, this class is deprecated—and using it can lead to class not found errors or initialization failures.

For Hibernate 4+, replace the provider_class property with the modern region factory:

<property name="hibernate.cache.region.factory_class">org.hibernate.cache.ehcache.EhCacheRegionFactory</property>

And double-check your build file (Maven/Gradle) includes the correct hibernate-ehcache artifact matching your Hibernate version—version mismatches are a super common culprit here.

2. Missing EhCache Configuration File #

Even with Hibernate’s cache settings enabled, EhCache needs its own config file (ehcache.xml) in your classpath to work properly. Without it, it’ll fall back to a minimal default setup that might not behave as you expect, or even fail to initialize.

Here’s a basic example ehcache.xml to get you started:

<ehcache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="ehcache.xsd"
         updateCheck="false"
         dynamicConfig="true">

    <defaultCache
            maxEntriesLocalHeap="10000"
            eternal="false"
            timeToIdleSeconds="120"
            timeToLiveSeconds="120"
            overflowToDisk="false"/>

    <!-- Add custom caches for specific entities if needed -->
    <cache name="com.yourpackage.YourEntity"
           maxEntriesLocalHeap="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="600"/>
</ehcache>

3. Entities Not Marked for Caching #

Enabling the global second-level cache doesn’t automatically cache all your entities—you need to explicitly mark which ones to cache:

• Annotation approach: Add @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) to your entity class (choose the strategy that fits your concurrency needs: READ_ONLY, NONSTRICT_READ_WRITE, etc.)
• XML mapping approach: Add <cache usage="read-write"/> inside your entity’s mapping definition.

Without this step, your entities won’t be stored in the second-level cache at all.

4. Query Cache Gotchas #

You’ve enabled use_query_cache, but keep these points in mind:

• Only queries you mark with setCacheable(true) (for HQL/Criteria) will use the query cache.
• Query cache relies on the second-level cache—so the entities returned by the query must already be configured for second-level caching.
• Query cache entries are invalidated when the underlying entity data changes, but complex queries joining multiple tables might need extra attention to avoid stale data.

5. Performance vs. Debug Tradeoff #

Your use_structured_entries is set to true—this makes cache entries easier to debug by storing them in a human-readable format, but it adds a small performance overhead. If you’re running in production and don’t need debug-level visibility, consider setting this to false to squeeze out a bit more performance.

If you’re hitting a specific error (like initialization exceptions, cache not working, or stale data), share the details and we can dive deeper. But these are the top areas to check first with your current config.

内容的提问来源于stack exchange，提问作者user83022