Uploaded image for project: 'Hibernate ORM'
  1. HHH-11276

JTA Transaction management with Spring and Weblogic broken

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects versions: None
    • Fix versions: None
    • Components: hibernate-core
    • Last commented by a user?:
      true
    • Sprint:

      Description

      This bug was first reported on the spring side here

      The sample project (that has to be deployed to weblogic) is available here (there are two projects actually, one with spring boot and another with plain spring mvc)

      When using hibernate 5.1.x and 5.2.x in combination with Spring and Weblogic, the jta transactions appear to break.

      Performing any type of database operation after a transaction was broken fails even if you specifically open a new one. Hibernate 5.0.x works perfectly fine.

      
      Caused by: java.sql.SQLException: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException: setRollbackOnly called on transaction]'. No further JDBC access is allowed within this transaction.
      
      

        Attachments

          Issue links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: