Hi all,

A have a question regarding the use of transactions. Is it safe to have several (non simultaneous) transactions in the scope of the same session ? I have serched the forums and the first conclusion would be - yes, it is possible - but we have a problem which we are thinking is related to this issue. The problem is that it is possible to have several transactions which are commiting themselves but in our case we would like to continue with the next transaction even if the previous one was rolled back. The problem here is that the session is never flushed on rollback and it seems that the database operations are still performed on the next transaction commit. A manual flush before the rolback solves this problem but it seems to be a little bit expensive. Is it possible/sane to have a possiblity to clear the session (manually or even better - automatically) on rollback ?

Thanks,
Peter.

You should not reuse the session after a rollback. You -may- use it across several -successful- transactions. (This is a kind-of "advanced" usage; Christian Bauer is the only guy I know who is actually doing this kind of thing in a real application.)

Thank you Gavin. I was expecting it to be possible as when you work directly with JDBC connections. I think I understand the problem with implementing this behaviour - the session cache remains inconsistent. For us it was interesting to have this as it is more transparent - we don't have to open another session if the transaction rollbacks and continue to use the same session as when the transaction succeeds. Maybe an Session.evictAll method would do the trick ? Anyway we will keep in mind this issue and will try to have a different code organisation.

Regards,
Peter.

I was looking through the hibernate beta3 version and there is a method Session.clear(). It seems to do exactly what I have asked for. Do you think using this method would allow the session reuse after a rollback ?

Thanks,
Peter.

Oh, sure, if you call clear(), the Session completely loses all state.