Environment: Hibernate 2.1RC1 + Spring 1.0 M4 + Ehcache
I want to use the read-write cache functionality but everytime the session looks up an object it has to be reread from the DB.
The class has an <cache usage="read-write"/> element and I've specified dynamic-update="false" and dynamic-insert="false".
The Session is the only current active session and there is no other transaction running at the moment.
Normally the last transaction should've unlocked every newloaded/modified cache item on commit but apparently this is not done.
So any ideas?

TIA
Sven

Are you sure that afterTransactionCompletion() gets called?

After some debugging I figured out that there is a bug in Hibernate or EHCache (depends who violated the contract):


isGettable always returned false because freshTimestamp was _always_ significant bigger than txTimestamp (e.g.
4384950622642176 vs.
1070544590106)
This happens because net.sf.ehcache.hibernate.Plugin.nextTimestamp uses Timestamper.next() but net.sf.ehcache.hibernate.Provider.nextTimestamp uses System.currentTimeMillis.

q.e.d.

Sven

I will fix ehcache

Can someone give an update on this?

I have Hibernate 2.1 final jar and the 0.6 release of ehcache and I'm still getting ttl exceeded:

2003-12-11 17:03:32,748 [Thread-10] DEBUG net.sf.ehcache.Cache - timeToLiveSeconds exceeded : 44702

even when ttl is set to 21600 (6 hours) and a make the requests within seconds of each other.

never mind, I didn't realize that the ehcache defaultCache doesn't provide a template for the subsequent <cache> elements. So I hadn't specified the ttl for each of my regions and I guess it defaults to 0s.