I am finding the onFlushDirty() method on my Interceptor is being repeatedly invoked when I would expect it to only be invoked once.

Here is the scenario:

I have a dirty entity. In the same session I have several calls to session.getNamedQuery().list(). Each of these calls triggers my Interceptor.

Here is what I see is happening:

Each call to session.getNamedQuery().list() makes a call to session.autoFlushIfRequired(), which ultimately calls session.flushEntity() for each entity in the session. For a dirty entity, this invokes my Interceptor. So far so good.

But the trouble is, since session.execute() is never called until I finally commit the transaction, the loadedState of the dirty entity never gets updated. Therefore each call to session.getNamedQuery().list() is triggering the interceptor. This does not seem correct behaviour to me.

I was wondering about setting the AutoFlush mode to Commit, but because I'm using spring's HibernateTransactionManager I'd rather not.

I'm using 2.1.7

Any ideas?

Perhaps I'm doing something wrong, but this seems like a bug to me.

I have an intereceptor set up, and in the code below each call to session.getNamedQuery() is triggering the interceptor. The only way round appears to be to set the flushMode to commit.

Sorry..........after several hours more debugging I've finally nailed this one down to a flawed hashCode(). My fault. I knew it would be.
Hibernate is God again.

What exactly was the problem with your haseCode()-method?