Hello hibernate users,

We’re currently upgrading our codebase from Hibernate 3 to Hibernate 4.3.7, and have run into an issue with the query cache during testing. Once a transaction has been committed, the cache is no longer being hit on subsequent queries. After some investigation we’ve found that it’s due to the UpdateTimestampsCache.invalidate method not being called when the transaction is committed. This leaves the UpdateTimestampsCache with the timestamps generated during the preinvalidate method, which includes the lock timeout duration (60s default), thus subsequent entries in the cache look out of date and aren’t used.

We are using SpringSessionContext, and it seems the implementation of SpringSessionSynchronization.afterCompletion has changed between hibernate 3 and 4 and no longer calls SessionImplementor.afterTransactionCompletion, which in turn lead to the UpdateTimestampsCache.invalidate being called. Has anyone encountered this issue already and know of a workaround?

Any assistance is much appreciated.

Make sure that you use Spring 4, and not Spring 3. According to Spring docs:

Hello, yes we are using Spring 4.2.6 and the hibernate4 library - org.springframework.orm.hibernate4.SpringSessionContext;

That's strange I summarized the Query Cache operations in this article.

Maybe you run into some bug. Unfortunately, Hibernate 4.x is not under development, so even if it's a bug, it will not be fixed. You'll have to test it against Hibernate 5.2, and if the bug replicates then we will fix it.

I've tested against Hibernate 5 and the issue still persists. Regardless of which version we're using, I'm confused as to how the query cache will work if the updateTimestampsCache is not invalidated after the transaction is committed. Any assistance is appreciated.

If you can come up with a replicating test case that demonstrates the issue, then you should open a bug for Hibernate 5.2.

I don't think it's a bug. What I see is that in SessionImplementor, the afterTransactionCompletion method is no longer present in version 4/5 as it was in 3. All we need to know is how we are supposed to perform the post transaction activities (such as invalidating the query cache) given that this method is deprecated.

The UpdateTimestampCache.invalidate method is called by the AfterTransactionCompletionProcessQueue callback of ActionQueue:



This callback is triggered by the afterTransactionCompletion method of the SessionImpl object.

As I mentioned in my original post - the implementation of SpringSessionSynchronization.afterCompletion has changed between hibernate 3 and 4 and no longer calls SessionImpl.afterTransactionCompletion.

As this issue resides inside the spring-orm-4.2.6 jar, I presume this is a spring ORM issue rather than hibernate then?

Yes. This is a Spring issue, and you should report it on their forum. Thanks.