Yes, we were eventually forced to call EntityManager.flush() in our application. But considering a large application with many APIs, this can't be done at API level. We came up with an AOP aspect to do achieve this. But considering the fact that hibernate is aware of J2EE environments through 'hibernate.transaction.jta.platform' setting, can it avoid calling 'setRollbackOnly' in SynchronizationCallbackCoordinatorImpl.beforeCompletion if the transaction manager is Weblogic's JTA transaction manager.