I have a test case where I save an object and then check to see if the id is set to a valid value.

If I have hibernate.connection.autocommit=false, then I get the next value in the sequence for the primary key but the object is not persisted to the database.

If I have hibernate.connection.autocommit=true, then the id is set to "0" but the object is persisted to the database.

I'm using db2 on a mainframe for the database. Has anyone else experienced this?

-Mike

Hello,

I've been experiencing the same problem as you describe.
I've reviewed all postings here and found that the DB2OS390 dialect would require the autocommit to false for the correct retrieval of the next value.

All objects and its collections are being inserted and updated but never actually commited into the tables.

Configuration is DB2 v7.1, JDBC Type2, Hibernate 3.x and using the OS390 dialect.

Has anyone experienced a similar problem? and if it can provide any pointers would be greately appreciated.

Finally on side testing we've confirmed the same code works fine on DB2Dialect (not os390) on a DB2 UDB 8.x on Windows.

Thanks !

Thanks for the reply! At least I feel a little more comfortable knowing others are still having this same problem. We've found a sort of work around for this. We are using spring with hibernate and we are using the hibernateTemplate that spring provides via extending HibernateDaoSupport. We are also using spring transactions. If we wrap all the daos in a transaction, then everything seems to work fine.

I can't say I understand why this works since hibernateTemplate should be able to figure out when to start/end a transaction, but if you use TransactionProxyFactoryBean then it runs the whole process in the same transaction and everything works.



hope this helps