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);
}

}
}



Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

If I understand you correctly, you want the update in transaction t1 to be rolled back if an error is generated in the following section of code:



Since you have already successfully committed the transaction t1 before you even execute the code above, then it is too late to try to rollback on transaction t1 if there is an error in transaction t2.

In your example, you'd want to move the t1.commit(); call to after the t2.commit() call. However, you could then get the situtation where the commit to t2 succeeds and the commit to t1 fails. If you want both transactions to succeed or both to fail, then what you really need is a two-phase commit.

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...

Thanks for the help guys.

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 guess I have to use JTA then. Thanks for the help !!!