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

Data inconsistency for CMR when connection is broken after database resource commits - missing fix from EAP 6.4

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • 7.0.0.DR5
    • 7.0.0.DR4
    • JCA, Transactions
    • None
    • Hide

      It could be run test case of crash recovery testsuite

      mvn clean verify -am -pl jbossts -DfailIfNoTests=false -Dtest=JPAProxyCMRCrashRecoveryTestCase#haltConnectionAfterDbCommits -Dno.cleanup.at.teardown -Djbossts.noJTS

      Show
      It could be run test case of crash recovery testsuite mvn clean verify -am -pl jbossts -DfailIfNoTests=false -Dtest=JPAProxyCMRCrashRecoveryTestCase#haltConnectionAfterDbCommits -Dno.cleanup.at.teardown -Djbossts.noJTS

      Fix of BZ#1181132 [1] for EAP 6.4 in ironjacamar is not ported to EAP7. IJ version under 6.4.0 is 1.0.31 and for 7.0.0.DR4 is 1.2.4 which are handled in different branches. It seems that fix with exception sorters was not moved there.

      As part of EAP 6.4 we have found issue for CMR where data inconsistency occurs. This happens when CMR db resource successfully commits but the connection is broken before TM receives confirmation about such state. As connection got broken XAException.XA_RBROLLBACK is thrown and TM decides to rollback whole XA transaction.
      That ends in situation where db resource was committed and other XA participants are rollbacked.

      Details are discussed at BZ#1181132 [1]

      [1] https://bugzilla.redhat.com/show_bug.cgi?id=1181132

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: