That's the thing Adelino Rodrigues. You could change the Hibernate code here just to confirm that this is the cause of the problem for WebLogic. But I personally look at it like that... this is a problem in WebLogic. I think this is a bad assumption/decision on WebLogic's part. I do not feel comfortable changing Hibernate upstream to not call setRollbackOnly.

That said, if you wanted to experiment you'd just change the implementation of org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.TransactionDriverControlImpl#markRollbackOnly. If that works for you, you could even consider developing a custom TransactionCoordinator implementation based on org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl that does not delegate the markRollbackOnly call when the JtaPlatform is WebLogic.