Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-20646

Hibernate claimEntityHolderIfPossible Assertion Error

XMLWordPrintable

    • Hide
      1. deploy attached project as a war to wildfly 36.0.1 with the -ea VM option.
      2. browse to http://localhost:8080/ee-reproducer/index.xhtml
      3. click the should not assert button and see it run successfully
      4. click the should assert button and observe a 

      Caused by: java.lang.AssertionError at org.hibernate@6.6.7.Final//org.hibernate.engine.internal.StatefulPersistenceContext.claimEntityHolderIfPossible(StatefulPersistenceContext.java:398)

      Show
      deploy attached project as a war to wildfly 36.0.1 with the -ea VM option. browse to http://localhost:8080/ee-reproducer/index.xhtml click the should not assert button and see it run successfully click the should assert button and observe a  Caused by: java.lang.AssertionError at org.hibernate@6.6.7.Final//org.hibernate.engine.internal.StatefulPersistenceContext.claimEntityHolderIfPossible(StatefulPersistenceContext.java:398)
    • ---
    • ---

      On a long mature wildfly ee10 project I ran into an issue trying to upgrade from 33.0.2 to 34.0.0

      The issue presents as an AssertionError with -ea on or simply a null pointer usually if assertions are not enabled.

      After much testing I've been able to distill this down to a very simple reproducer war.

      I have tried to get a hibernate test case to fail to no success so I think this may have to do with the integration or enhancements with wildfly + hibernate.

        1. ee-reproducer-hibernate-assert.zip
          16 kB

              smarlow1@redhat.com Scott Marlow
              cody.lerum@gmail.com Cody Lerum
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: