We had been using Hibernate 3.2.0 with WebSphere 6.1.0.2 through WebSphereExtendedJTATransactionLookup for over a year. This past weekend we updated to WebSphere 6.1.0.9 and began to see UnsupportedOperationExceptions from the setRollbackOnly method.

Looking at the current Hibernate source it looks like setRollbackOnly always throws that exception so I can only assume it wasn't being called with WebSphere 6.1.0.2. Here's the pertinent portion of the current stack trace:
at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:63)
at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$1.invoke(WebSphereExtendedJTATransactionLookup.java:136)
at $Proxy3.beforeCompletion(Unknown Source)
at com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCompletion(SynchronizationCallbackWrapper.java:65)
at com.ibm.ws.Transaction.JTA.RegisteredSyncs.distributeBefore(RegisteredSyncs.java:242)
at com.ibm.ws.Transaction.JTA.TransactionImpl.prePrepare(TransactionImpl.java:2389)
at com.ibm.ws.Transaction.JTA.TransactionImpl.stage1CommitProcessing(TransactionImpl.java:1622)
at com.ibm.ws.Transaction.JTA.TransactionImpl.processCommit(TransactionImpl.java:1593)
at com.ibm.ws.Transaction.JTA.TransactionImpl.commit(TransactionImpl.java:1528)
at com.ibm.ws.Transaction.JTA.TranManagerImpl.commit(TranManagerImpl.java:237)
at com.ibm.ws.Transaction.JTA.TranManagerSet.commit(TranManagerSet.java:162)
at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:756)
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:181)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:581)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3910)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3732)
...

Any suggestions on how I can resolve this problem (other than rolling back WebSphere 6.1.0.9 as we need that version for other reasons) would be greatly appreciated.

- Mike