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

There are in doubt transactions after communication DB to EAP is halted

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 12.0.0.Final
    • 11.0.0.Final
    • Transactions
    • None
    • Hide

      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/tests-transactions.git -b master
      export JBOSS_HOME=(downloaded CR1)
      mvn clean verify -Djboss.dist=$JBOSS_HOME '-Dtest=JMSProxy*MessagingServerCrashRecoveryTestCase#haltConnectionAfterDbCommits*' -B -Dmaven.test.failure.ignore=true -Dsurefire.test.failure.ignore=true -fn -Dsurefire.rerunFailingTestsCount=1 -Dsurefire.forked.process.timeout=0 -Deap -Dversion.eap=7.1.0.GA-redhat-6 -Dproxy.port=12345 -Dts.jbossts1.node.identifier=aXbG -Dts.jbossts2.node.identifier=IyJc -Dts.jbossts3.node.identifier=CPXo -Djournal.objectstore.asyncio=true -Djbossts.objectstore.type=activemq -Dts.timeout.factor=150 -DfailIfNoTests=false

      Show
      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/tests-transactions.git -b master export JBOSS_HOME=(downloaded CR1) mvn clean verify -Djboss.dist=$JBOSS_HOME '-Dtest=JMSProxy*MessagingServerCrashRecoveryTestCase#haltConnectionAfterDbCommits*' -B -Dmaven.test.failure.ignore=true -Dsurefire.test.failure.ignore=true -fn -Dsurefire.rerunFailingTestsCount=1 -Dsurefire.forked.process.timeout=0 -Deap -Dversion.eap=7.1.0.GA-redhat-6 -Dproxy.port=12345 -Dts.jbossts1.node.identifier=aXbG -Dts.jbossts2.node.identifier=IyJc -Dts.jbossts3.node.identifier=CPXo -Djournal.objectstore.asyncio=true -Djbossts.objectstore.type=activemq -Dts.timeout.factor=150 -DfailIfNoTests=false

    Description

      Implementation: JTS

      Priority is set to critical due to regression (issue is not seen in 7.0) and the fact that some inconsistency might be expected (communication from DB to EAP is halted - resource is commited, but TM doesn't know it)

      Failing tests:
      org.jboss.as.test.jbossts.crashrec.test.JMSProxyMdbMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA(org.jboss.as.test.jbossts.crashrec.test.JMSProxyMdbMessagingServerCrashRecoveryTestCase)
      Run 1: JMSProxyMdbMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA:276->TestBaseOneServer.checkIfTxLogsAreEmpty:564->TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy:619 Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: 0:ffff7f000001:-5d473c0b:59afe2ee:69[["0:ffff7f000001:-5d473c0b:59afe2ee:7c"]],
      Run 2: JMSProxyMdbMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA JBoss log parsed file /home/istraka/repositories/jboss-other-repositories/tests-transactions/jbossts/target/jbossas-jbossts/standalone/log/JMSProxyMdbMessagingServerCrashRecoveryTestCase_haltConnectionAfterDbCommitsWithTestXA_jts_server.log contains not expected string XAException on line 11313 with text '2017-09-06 14:00:32,786 WARN [com.arjuna.ats.jtax] (Periodic Recovery) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_NOTA from resource XAResourceWrapperImpl@46c7baf5[xaResource=org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper@4d2dca8d pad=false overrideRmValue=null productName=ActiveMQ Artemis productVersion=2.0 jndiName=java:/JmsXA NodeId:846be472-92f7-11e7-b284-340286a805f7] in transaction < 131072, 32, 36, 0000000000-1-1127001-94-72-61-1189-81-30-1800010597889871, 0000000000-1-1127001-94-72-61-1189-81-30-1800012300000000 >: javax.transaction.xa.XAException'

      org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommits(org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase)
      Run 1: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommits:277->TestBaseOneServer.checkIfTxLogsAreEmpty:564->TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy:619 Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: 0:ffff7f000001:-a865f1e:59afdfbb:64[["0:ffff7f000001:-a865f1e:59afdfbb:6e"]],
      Run 2: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommits JBoss log parsed file /home/istraka/repositories/jboss-other-repositories/tests-transactions/jbossts/target/jbossas-jbossts/standalone/log/JMSProxyMessagingServerCrashRecoveryTestCase_haltConnectionAfterDbCommits_jts_server.log contains not expected string XAException on line 5951 with text '2017-09-06 13:46:42,888 WARN [com.arjuna.ats.jtax] (Periodic Recovery) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_NOTA from resource XAResourceWrapperImpl@730871ea[xaResource=org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper@4028496b pad=false overrideRmValue=null productName=ActiveMQ Artemis productVersion=2.0 jndiName=java:/JmsXA NodeId:846be472-92f7-11e7-b284-340286a805f7] in transaction < 131072, 32, 36, 0000000000-1-1127001-11121-96-3089-81-33-6900010097889871, 0000000000-1-1127001-11121-96-3089-81-33-6900010900000000 >: javax.transaction.xa.XAException'

      org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA(org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase)
      Run 1: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA:289->TestBaseOneServer.checkIfTxLogsAreEmpty:564->TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy:619 Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: 0:ffff7f000001:4087749a:59afe058:64[["0:ffff7f000001:4087749a:59afe058:73"]],
      Run 2: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA JBoss log parsed file /home/istraka/repositories/jboss-other-repositories/tests-transactions/jbossts/target/jbossas-jbossts/standalone/log/JMSProxyMessagingServerCrashRecoveryTestCase_haltConnectionAfterDbCommitsWithTestXA_jts_server.log contains not expected string XAException on line 5996 with text '2017-09-06 13:49:18,766 WARN [com.arjuna.ats.jtax] (Periodic Recovery) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_NOTA from resource XAResourceWrapperImpl@1bb543cb[xaResource=org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper@1e73c422 pad=false overrideRmValue=null productName=ActiveMQ Artemis productVersion=2.0 jndiName=java:/JmsXA NodeId:846be472-92f7-11e7-b284-340286a805f7] in transaction < 131072, 32, 36, 0000000000-1-112700164-121116-10289-81-328800010097889871, 0000000000-1-112700164-121116-10289-81-328800011400000000 >: javax.transaction.xa.XAException'

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13023 There are in doubt transactions after communication DB to EAP is halted

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-9915 Component upgrade of Narayana to 5.8.0.Final

          • 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
          relates 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) JBTM-2939 JTS for not putting transaction to heuristic state during recovery for XAException.XAER_NOTA

          • 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:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: