I have a need to update one table based on previous transaction result. However, if the update failed, the previous transaction should rollback. I have the following code trying to do so but it does not seen to work. Any help is appreciated.
------------------------------

Hibernate version:2.01

Mapping documents:

Code between sessionFactory.openSession() and session.close():

// get a hiberate open session

Session session = sessionFactory.openSession();

Transaction t1 = session.beginTransaction();
Transaction t2 = session.beginTransaction();
try
{
// insert a new row in Table1

tk = something ....

session.save(tk);
session.flush();
t1.commit();


// Based on new information of tk, update Table2
// but if update failed, I want to roll back Table1 transaction.

tkper.setTKId(tk);
session.update(tkper);

session.flush();
t2.commit();
session.close();

}
catch (HibernateException e)
{
t1.rollback(); // does not seen to work.
t2.rollback();
logger.error("Hibernate Exception" + e.getMessage());
throw new RuntimeException(e);
}
finally
{
if (session != null)
{
try
{

session.close();
}
catch (HibernateException e)
{
logger.error("Hibernate Exception" + e.getMessage());
throw new RuntimeException(e);
}

}
}

You can't do a rollback after a commit, it's too late. If you need the save() inside to be rolled back when the update() fails, use a single transaction around both.

If you are using the JDBCTransactionManager - thus not using JTA - you cannot have nested transactions.

As I can see, you two transactions come from the same Hibernate session, and therefore the same JDBC connection...

The reason that I have to commit the first transaction is that it does not seen to give the lastest sequence number (DB trigger generated) of Table1 unless it is commited. This sequence number is needed for the second transaction.

I had the JDBCTransaction manager:

hibernate.transaction.factory_class=net.sf.hibernate.transaction.JDBCTransactionFactory

Do I need to change the following : ??

hibernate.transaction.factory_class=net.sf.hibernate.transaction.JTATransactionFactory

-------------
How do I do any nested transaction ?

As far as I know, JDBC doesn't support nested transactions at all.
In your example, you have nested transactions since you create two transactions from the same Hibernate session - and therefore the same JDBC connection (one per session). The 2nd transaction is then nested inside the first ;)


Changing to the JTA transaction is meaningfull only if you have a JTA transaction manager... most probably inside a full-blown app-server like JBoss.

I think you should look for another way to autoincrement the value that now incremented by your trigger via sequence number. In your case the two operations should be inside one transaction and you don't need any nested one.

What value do you need to autoincrement? If it is some property of the first object (tk), try this, it should work: