version rollback on transaction.rollback() error

rihards · **Joined:** Tue Apr 13, 2004 6:41 am **Posts:** 19

Hibernate version: 2.1.6

It looks like that hibernate does not rollback version of object when it fails...

I am using optimistic-lock="version" class mapping strategy to determine if instance is new. What happens is that if .commit() fails and I do tx.rollback() version values are not reverted back, so I can not use these instances anymore, because version information for them is incorrect!!!

Is this bug or feature???

Documentation does not say that instance become invalid when tx.commit() fails, it just says that session becomes invalid and it is necessary to do rollback()...

Rihards

rihards · **Joined:** Tue Apr 13, 2004 6:41 am **Posts:** 19

so it is bug or not? for it looks like it is, because I can not actualy use these objects anymore, because of invalid version information...

rihards · **Joined:** Tue Apr 13, 2004 6:41 am **Posts:** 19

hello?

rghome · **Posted:** Thu Oct 14, 2004 10:52 am

I think you should say which transaction manager you are using. For example, if you are using the JDBC transaction manager, then Hibernate just calls rollback() on the JDBC connection. So it should not matter what Hibernate does - it shouldn't get through to the database.