[TAP5-137] org.hibernate.TransactionException thrown when a transaction is directly rolledback (outside of tapestry-hibernate)

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Abandoned
• Affects Version/s: 5.0.15
• Assignee: Howard Lewis Ship
• Reporter: Joe Klecko
• Created: 11/Sep/08 02:33
• Updated: 23/Nov/11 19:06
• Resolved: 23/Nov/11 19:06

Description

A "org.hibernate.TransactionException: Transaction not successfully started " occurs when a transaction is rolledback in tapestry-hibernate if the transaction has previously been rolledback. The problem is because HibernateSessionManagerImpl retains a reference to the transaction. So when HibernateSessionManagerImpl .threadDidCleanup() or HibernateSessionManagerImpl abort() is called it does not first check to see if the transaction reference has been rolled back (somewhere else) before calling rollback. One possible fix would be to call Transaction.wasRolledback() to determine if tapestry-hibernate should call trans.rollback(). Another would be to refrain from keeping a reference to the transaction and always call Session.beginTransaction().

Q. Why not just inject HibernateSessionManager and call abort()?
A. Because there are times when you do not have control over the code calling trans.rollback() for example in a third party library (which is how I ran into this).