Hello, I am using direct SQL to update a table that has a second level cache (EhCache) with read-write concurrency. Rows updated with direct SQL which are in the second level cache need to be refreshed in the cache in order to be in synch with the database. Is it possible to refresh the second level cache or even to clear it so Hibernate will reread the underlying database? If so, how?
Peter

Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.0.5

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using: MySQL 4.1.11-nt

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

check out: sessionFactory.evict* methods... they'll let you clear one or many objects at a time (per class).

It appears that sessionFactory.evict deals with the session not the second level cache (ehcache in this case). I did try using evict but it only evicts from the session. The now-obsolete entries in ehcache are still there and will be used to repopulate the object into the session, with obsolete data.

I need to be able to tell the second level cache (ehcache) to refresh its contents or clear its contents. Is there a way to do that?

Check again.
According to the V3 reference doc :

"For the second-level cache, there are methods defined on SessionFactory for evicting the cached state of an instance, entire class, collection instance or entire collection role."

ehcache is your first-level of cache (it is only for the current session). 2nd level cache is managed by SessionFactory and spans sessions (within a JVM, and actually supposed to work in cluster - never tried that however)... Try evicting/flush..etc. from each of the session and sessionfactory and you should be able to get the results - I'd think - if not post some sample code and I'll see if I can help with what you're doing...

sorry, mispoke ehcache manages your 2nd level cache JVM-Level (I just checked the manual)...the rest of what I said about session & factory should work.

Thanks for the suggestion and information. Session flush, evict and refresh were tried with apparently no effect on ehcache evidenced by the non-updated rows being returned despite the database having been updated. It's as if the 1st and 2nd level caches are simply independent. And I'm OK with that I just need a way for Hibernate to tell the 2nd level cache to refresh itself or clear itself or a way to directly access the 2nd level cache. For example, would the ehcache CacheManager work for this?

In the meantime I will try to put together an example of the problem.