Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6096

UNSYNCHRONIZED extended persistence context associated but not joined with JTA transaction and target component is persistence context of SYNCHRONIZED, IllegalStateException should be thrown


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR6
    • 7.0.0.GA, 7.1.0.DR5
    • JPA/Hibernate
    • None

      As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.

      The obtained defect:
      A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section was found in WildFly 10.1.0.Final.
      The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)

      We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
      Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e69c562c40
      Changes: The method getSynchronizationType returns declared synchronization type.

            smarlow1@redhat.com Scott Marlow
            smarlow1@redhat.com Scott Marlow
            kostd kostd (Inactive)
            0 Vote for this issue
            3 Start watching this issue