I am using hibernate 3.1.3 in a JTA managed transaction.
Under certain circumstances when I issue the commit() on the
UserTransaction the datastore raises an exception when hibernate flushes its pending modifications.
The exception is ignored by the TransactionManager (JOTM) in terms of decision whether commit or not,
so the resource is committed.
Is there anyone who has experienced the same problem ?
AFAICS, hibernate session flushes pending modifications by the mean of a
Synchronization object in its beforeCompletion() method.
I think that there is a flaw in this approach unless a setRollbackOnly() is issued in case of exception.
In fact, transaction manager, on commit(), calls beforeCompletion() before starting 2PC and
control to the application is return after the 2PC protocol is ended.
There is no way for the application to catch hibernate exception in time to
decide to rollback.
The complete environment consists in:
hibernate 3.1.3
JOTM 2.x
XAPOOL 1.5
Plain MS SQL Server JDBC driver.

Any luck with this problem? I'm having the same problem. Apparently Jotm fixed this in 2.0.12 http://forge.objectweb.org/tracker/?fun ... roup_id=19

However, I'm also getting this problem in Websphere's TX mngr.

Mike