When my Stored Procedures are executed and I throw an exception, the data stored in the SP don't roll back.

My question is... using the connection obtained through the session, would it be in the same transaction of the session?

Sample:

try
{
getSession().beginTransaction();

// ....

Connection conn = session.connection();
CallableStatement callStmt = conn.prepareCall(chamada);
stmt.executeUpdate();

// ..... (manipulate objects..)

getTransaction().commit();
}catch(Exception ex)
{
getTransaction().rollback();
}


Thanks

Yes it is, since it's the same connection

So I don't understand what is happening... the SP doesn't have "commit" and the data inserted into the SP isn't rolled back when ocurring an exception.

Any idea? I tried to set the autocommit false into the connection, it worked, but doesn't make sense and the data take too long to be commited at all.

autocommit *must* be set to false, and you transaction be explicit using bsession.beginTransaction and tx.commit(); otherwise you"re not in the same tx, since the JDBC driver will create a new one for every single statement.

Thank you very much, Emmanuel!
It's clearer now. :)

Just one more doubt... like I told before it works when I set the autocommit to false, but after the process finish to run the table keeps locked and the data take a while (5 - 10 seconds) to appear into the DB.

Is it usual to happen that? It's just a small register hardcoded inserted in a table in the SP. When I make conn.commit doesn't have this delay.

Thanks again.

Solve it! :)
Thanks everybody!

Now it was my mistake...

It works like expected. :)