Greets,

using hibernate 2.1.4

Is this normal or abnormal behavior of evict? (we are using hibernate's cache as peristable object cache in unit_of_work)

{
session.save(someObject); //cache object

(do some stuff w/someObject...and then decide to remove it)

session.evict(someObject); //remove ghost from cache

session.flush();

(commit transaction etc..)
}

previous example throws:
net.sf.hibernate.AssertionFailure: possible nonthreadsafe access to session

as flush still seems to try save evicted object into db.

Problem is, that Im flushing at the very end of transaction flow, (adding flush() between save and evict removes exception, but I do not want to save data before end).

Any workaround available or so?

Thanks,

Hibernate 3.0

I have exactly the same problem:



What am I doing wrong?

I guess it was a stupid question... if I've evicted the entity from cache the commit() will not find it there! The error message confused me a little.

I've tried to use StatelessSession but I was hoping to take advantage of transactional write behind. My error

Try using flush() between save and evict. Hibernate is trying to protect you from evicting something that isn't in persistent state.

I experienced the same problem. The question is, if the session is must be flushed before I evict something and Hibernate is "protecting me", then why doesn't Hibernate just flush it for me? Especially, since I have flushmode set to AUTO!

It's pretty confusing getting a "nonthreadsafe" assertion when using known "Thread-safe" wrapper like HibernateTemplate for all of your operations just because you evicted something you previously saved (but before flush). It was especially odd getting it in a single transaction inside a single method of a single unit test. Umm... I only HAVE one thread!