Hello,


I already see post about this problem, it was said that it can due to transaction and session because the object are already in data base or not.
The problem is that I have an interceptor that manage the transaction and the session, so that is not the problem !!?

In fact I have an entry, when I update it, it is ok, but if I delete it and then I try to save it, this problem occurs?

Have you any idea to solve this problem ?

I have similar problem. I verified that hibernate session is closed and there is no session leak. However, once the problem occurs, it stay there forever, for all new transaction and new session.

So it does not seems to me the problem of session cache. Is there a global cache in hibernate? If yes, how can I clear it?

The problem has haunted me for quite some time, very difficult to reproduce, and difficult to get rid of it once occurred.

What method are you calling to persist the object. This sounds like you're trying to call Session.update on an object that has not been persisted yet. Try saveOrUpdate.

Precisely, I am using saveOrUpdate to persist my data !

In my case, I can reproduce the action.
In fact, I have save an entry in my data base (this entry = object with a collection of string).
If I import the same object (this must be updated). It works...

But if I delete the entry and just after I get the same objet and I try to save it, the error occurs...