Hi all,

I've implemented a TransactionManagerLookup that supports the new UOW feature from newer WebSphere 6.1 and 7.0. Its implementation is simpler than the previous one since it does not require the proxies for custom IBM APIs(WAS now supports javax.transaction.Synchronization). It also supports setting setRollbackOnly (that was unsupported on previous versions).

How could I submit this to Hibernate team for it to be evaluated and possibly integrated into Hibernate? Should I open a Jira issue and attach the file?

best regards,
Rafael Ribeiro

If anyone is interested in testing a draft implementation of the mentioned TransactionManagerLookup, please take a look at: http://itdevworld.wordpress.com/2009/01/23/websphere-uow-transactionmanagerlookup-for-hibernate/

Hello rafaelri,

Thanks for your info. There were many posts related to this problem (setRollbackOnly call in Hibernate's CacheSynchronization class fails with UnsupportedOperationException due to WebSphereExtendedTransactionManagerLookup class implementation) and on this forum too (for example here, here and here). But silence was the only result. You are the one who propose the solution.

There is also corresponding bugs in Hibernate JIRA: HHH-2124 and HHH-2703

We've also experienced this problem (Hibernate 3.3.1GA + WebSphere 6.1.0.21 + Oracle 9.2.0.7) and found that using new WebSphere UOW API might resolve this problem. I added corresponding comment to HHH-2124 and HHH-2703.

We haven't tried your solution yet, but I was able to rollback JTA transaction through this WebSphere UOW API.

Let's hope that Hibernate developers will pay some attention to us and add corresponding changes to WebSphereExtendedTransactionManagerLookup class.