After looking at the attached jpa_stack_trace.txt, I'm wondering what would happen (with WebLogic) if Hibernate did not call transactionCoordinator.setRollbackOnly(), but instead only threw the exceptionMapper.mapStatusCheckFailure(...).

Adelino Rodrigues would it be possible for you to experiment with trying that, just so we can learn if this is a WebLogic bug (feature?) that can be worked around by not setting rollback only. If you have the itch to build Hibernate ORM with a code change like that, it could help the discussion here. What do you think?