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

(7.3.z) WFTC registry records may not be removed during the OpenShift scale down processing when transaction recovery commits

    XMLWordPrintable

Details

    • +
    • Hide

      There is test in OpenShift testsuite (see step for reproduce at WFLY-12922

      mvn clean test -P72 -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -Dconsole-log-level=DEBUG

      There is an integration test in EAP QE crashrec testsuite

      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/tests-transactions.git
mvn clean verify -am -pl jbossts -DfailIfNoTests=false -Djbossts.noJTS -Djboss.dist=$JBOSS_HOME -Dtest=TxPropagationJMSCrashRecoveryTestCase#injectRmfailAtServerCommit
      Show
      There is test in OpenShift testsuite (see step for reproduce at WFLY-12922 mvn clean test -P72 -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -Dconsole-log-level=DEBUG There is an integration test in EAP QE crashrec testsuite git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/tests-transactions.git mvn clean verify -am -pl jbossts -DfailIfNoTests= false -Djbossts.noJTS -Djboss.dist=$JBOSS_HOME -Dtest=TxPropagationJMSCrashRecoveryTestCase#injectRmfailAtServerCommit

    Description

      The OpenShift scale down processing may cause not removing the WFTC registry record.
      This may happen when the EAP runs the EJB remote call with transaction context propagation (the EAP1 calls the EAP2). When the transaction processing fails (e.g. JVM crashes or intermittent network failure happens) after the prepare phase finishes (commit of the resource is expected) and recovery processing tries to commit the transaction afterwards. If in the same time scale down recovery processing is launched from the OpenShift WildFly operator then the commit is processed successfully - all the transaction participants are committed on EAP1 and EAP2 - but EAP1 does not remove WFTC XAResourceRegistry record (a file saved on the file system at EAP1 and which is required for successful recovery processing). Record could not be never removed and it may stuck OpenShift scaledown process as for smooth scaledown there can't be any XAResourceRegistry record. EAP1 could be then stuck during the scaled down.

      This is a follow-up (or kind of clone) of issue WFLY-12922 which talks exactly about this issue. The WFLY-12922 was fixed by change WFTC-77. But later it was found that change causes a regression JBEAP-19408 and the fix WFTC-77 was reverted by WFTC-82.

      There is need to find a way for removing WFTC XAResourceRegistry record immediately during the recovery commit.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFTC-85 XAResourceRegistry record needs to be clean immediatelly after commit is called even during recovery

          • 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.
          • Resolved
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFTC-85 XAResourceRegistry record needs to be clean immediatelly after commit is called even during recovery

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-20037 [GSS](7.3.z) Upgrade wildfly-transaction-client from 1.1.11.Final-redhat-00001 to 1.1.13.Final-redhat-00001

          • 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.
          • Closed
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-13578 Add a testcase for transaction propagation over EJB remote simulating network issues on remote calls

          • 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.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19408 [QE](7.3.z) Unfinished transactions in JMS crash recovery scenario using JTA

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19423 [QE](7.2.z) WFTC-82 - Unfinished transactions in JMS crash recovery scenario using JTA

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFTC-82 XAResourceRegistry record cleanup cannot be permitted for XAResource.recover(TMENDRSCAN)

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFTC-77 Provide correct integration of SubordinateXAResource with Narayana recovery

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFLY-12922 server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

          • 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.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: