Anyone willing to pick this up and try with Hibernate 5.0? If the cause is really the use of setRollbackOnly in WebLogic then the issue is likely still there.

For what its worth, we had to deal with this in JBossTS as well quite some time ago. They now have a very reasonable, robust handling for this. WebLogic apparently does not.

We could also skip the setRollbackOnly call for known JtaPlatforms indicating WebLogic. It does remove a bit of safety however. But if you are using WebLogic, there does not seem to be any way around this. However, since we expose this from our Transaction API, I do worry about how we know which setRollbackOnly calls to skip and which ones we should not.