Clearing Hibernate Second-Level Caches
Recently, I wanted to be able to clear out all of the Hibernate caches
via JBoss's JMX console. I could have taken the easy way out; we're
using EHCache, so it could have been as simple as calling CacheManager.clearAll().
However, that would have tied me to a specific cache provider. We're
still evaluating switching to other cache providers. Ideally, my
solution would not be dependent on a specific cache implementation.
Hibernate's
API does provide a simple way to clear specific caches, but does not
provide any method for clearing out all of them. Writing your own is
fairly straightforward. First, you obtain all of the entity and
collection metadata from the session factory. Next you iterate over the
entities, and if the object is cached, you clear out all of the caches
associated with the persisted class or collection. Here's the code:
@PersistenceContext
private EntityManager em;
public void clearHibernateCache() {
Session s = (Session)em.getDelegate();
SessionFactory sf = s.getSessionFactory();
Map classMetadata = sf.getAllClassMetadata();
for (EntityPersister ep : classMetadata.values()) {
if (ep.hasCache()) {
sf.evictEntity(ep.getCache().getRegionName());
}
}
Map collMetadata = sf.getAllCollectionMetadata();
for (AbstractCollectionPersister acp : collMetadata.values()) {
if (acp.hasCache()) {
sf.evictCollection(acp.getCache().getRegionName());
}
}
return;
}
Now, if we decide to switch to a different cache provider, this code will not need to be re-written. Hopefully we won't ever change to a different JPA implementaion. :)
From http://mikedesjardins.us/blog/
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)






Comments
Shashi Velur replied on Fri, 2008/10/24 - 4:35pm
Yeah, we had a similar situation in our application to programmatically clear the Hibernate Level 2 cache only once during the application startup (after making some huge schema/DDL changes).
We got around that by closing the current Sessionfactory and creating a new one. The lifecycle of Hibernate Level 2 cache is dependent upon that of the Hibernate SessionFactory.
For your situation, I guess your approach works best. :)
Galder Zamarreno replied on Wed, 2012/02/22 - 10:45am
Steve Ebersole replied on Wed, 2012/02/22 - 11:11am
Mike, why not just use the SessionFactory#getCache() API? In fact the methods you metioned (SessionFactory#evictEntity, etc) are all deprecated in favor of going through SessionFactory#getCache()...
There was some question initially about whether calling evictQueryRegions() should imply evictDefaultQueryRegion(). As of today it does not.
There is currently not a way to manually evict the update-timestamp cache