Hibernate version:
3.0.3

What other reason could their be for a collection being evicted from the session if

A) We are dealing with the same session for the entire thread
B) Evict() was never called

I'm noticing that, after a rollback in a transaction, I'm losing one of my collections.

Yeah, from my experience, you need to close your session and open a new one after a rollback.

Interesting....since all of my calls to my DAOs are through a service, and the service methods are transacted (I'm using Spring's transaction demarcation system), I'm wondering where I will call open/close. It should really happen in Spring's transaction manager. Seems like a waste of cycles, however, as close/open will invalidate the cache and detach all existing objects

Will lazy loading on a detached object work after closing/opening the session?

In my case, the session is attached to a threadlocal object.

Coworker ran into this earlier this morning as well, no evict getting called but haven't taken the time to sit down and see what was going on. If you find out be sure to post.

Ok, perhaps I have some light to shed on this.

For us, it seems to happen if we load up a collection of objects from DB and start iterating through them, call clear() on the session and then call a property on any of the objects that will trigger a lazy load.

Would the solution for this be to lock the object back into the session as we process each one? We're calling clear since we're in a rather large piece of work and want to keep the mem usage in check.

Would something like evict() be a preferred technique in this case?