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

Sometimes happens that jta-crash-rec quickstart fails after scaling up EAP deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 7.2.0.GA
    • OpenShift
    • None
    • Hide

      Configure DNS server in your /etc/resolv.conf - add:

      nameserver 10.0.144.45

      Follow those steps to run test against OCP 3.11 cluster - not 100% reproducer :

      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/openshift-eap-tests.git
cd openshift-eap-tests
git checkout master
# create test.properties file and set correct *.url and *.token
xtf.config.domain=all-in-one-034.dynamic.xpaas
xtf.openshift.namespace=dev-testsuite-namespace
xtf.bm.namespace=dev-builds

Start test by:
mvn clean test -P72 -Dtest=JtaCrashRecQuickstartTest#testJTAXaRecovery
      Show
      Configure DNS server in your /etc/resolv.conf - add: nameserver 10.0.144.45 Follow those steps to run test against OCP 3.11 cluster - not 100% reproducer : git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/openshift-eap-tests.git cd openshift-eap-tests git checkout master # create test.properties file and set correct *.url and *.token xtf.config.domain=all-in-one-034.dynamic.xpaas xtf.openshift.namespace=dev-testsuite-namespace xtf.bm.namespace=dev-builds Start test by: mvn clean test -P72 -Dtest=JtaCrashRecQuickstartTest#testJTAXaRecovery

      jta-crash-rec quick start [1] sometimes fails on not properly recovering XA transaction.

      The issue happens once pod with EAP is scaled up again. There should be record Rover updated via JMS in H2 database.

      By checking transaction logs there is issue that original EAP server, MDB commits subtransaction for H2 database but subtransaction for AMQ is in prepared state. XA transaction in such state should be committed by recovery manager.
      However migration pod (with recovery manager) rolled back AMQ subtransaction. What is weird that commit for H2 database is not visible after scaling up the pod with EAP.

      It's probable that all issues are caused by H2 database which is not reliable for this use case. See linked issue CLOUD-2795

      [1] https://github.com/jboss-openshift/openshift-quickstarts/tree/master/jta-crash-rec-eap

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

                Created:
                Updated:
                Resolved: