Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2907

Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 5.5.25.Final, 5.6.2.Final
    • 5.2.24.Final, 5.6.1.Final
    • JTS
    • None
    • Hide

      Crash recovery testsuite testcase could be used

      export JBOSS_HOME=...
mvn clean verify -am -pl jbossts -DfailIfNoTests=false -fn -Djbossts.noJTA -Dtest=JcaInflowTransactionTestCase#jvmCrashAfterPrepareJTS -Deap -Dversion.eap=7.1.0.Beta1-redhat-4
      Show
      Crash recovery testsuite testcase could be used export JBOSS_HOME=... mvn clean verify -am -pl jbossts -DfailIfNoTests= false -fn -Djbossts.noJTA -Dtest=JcaInflowTransactionTestCase#jvmCrashAfterPrepareJTS -Deap -Dversion.eap=7.1.0.Beta1-redhat-4

    Description

      When RAR calls XATerminator.recover(int) the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where ExtendedJBossXATerminator method doRecover is called. But the doRecover does not provide the expected recovery call - e.g. it does not accept flags (XAResource.TMSTARTRSCAN, XAResource.TMENDRSCAN) to drive the whole recovery process in case.

      The biggest functionality trouble is for JTS where XATerminatorImple does not implement intentionally the doRecover function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/jca/XATerminatorImple.java#L511). Thus RAR using call XATerminator.recover when JTS is under use does nothing.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11528 Call of JCA RAR XATerminator.recover does not propagate to correct implementation of Narayana terminator

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11154 JCA inflow transaction committed by recovery is not removed from tx log when JTS is used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: