Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-9867

Message loss after a server restart in the collocated HA cluster with JDBC store journal

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • AMQ 7.13.0.GA
    • jdbc, journal
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Steps to reproduce (issue is intermittent):

      git clone git@gitlab.cee.redhat.com:jbossqe-eap/messaging-testsuite.git messaging-testsuite
cd messaging-testsuite/scripts/

groovy -DEAP_ZIP_URL=<path_to_server_zip_file> PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/
mvn clean install -B -Dversion.artemis=2.40.0 -Dsurefire.timeout=93600 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1749848644-SNAPSHOT -Deap7.clients.version=8.1749848644-SNAPSHOT -Dsurefire.failIfNoSpecifiedTests=false -Dprepare.param.DATABASE=db2_115 -Dprepare.param.JDBC_STORE=true -Dtestsuite.db.dballocator.force.list=db2_115 -Dtest=ColocatedClusterFailoverTestCase#testFailbackWithMdbsShutdown
      Show
      Steps to reproduce (issue is intermittent): git clone git@gitlab.cee.redhat.com:jbossqe-eap/messaging-testsuite.git messaging-testsuite cd messaging-testsuite/scripts/ groovy -DEAP_ZIP_URL=<path_to_server_zip_file> PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean install -B -Dversion.artemis=2.40.0 -Dsurefire.timeout=93600 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1749848644-SNAPSHOT -Deap7.clients.version=8.1749848644-SNAPSHOT -Dsurefire.failIfNoSpecifiedTests= false -Dprepare.param.DATABASE=db2_115 -Dprepare.param.JDBC_STORE= true -Dtestsuite.db.dballocator.force.list=db2_115 -Dtest=ColocatedClusterFailoverTestCase#testFailbackWithMdbsShutdown

      When using DB2 as a JDBC store, some messages are lost during failover scenario. This was observed when a message was redistributed to a shutting-down node, which acknowledged it but did not persist it. The behavior is similar to previously reported issue JBEAP-29281 with file-based journal. Detailed trace logs are available for further analysis.

      Customer impact: In a collocated HA topology, if one of the EAP servers is shut down and restarted (a standard administrative operation) there is a possibility that one or more messages may be lost.

      Test Scenario:

      • start two EAP servers in colocated HA topology in cluster with InQueue and OutQueue
      • start producer to each of the servers and send 6000 messages to InQueue
      • deploy MDBs to 2nd node which consumes messages from InQueue and resends new message to OutQueue
      • wait until some messages are processed
      • shut down node-2
      • check if backup server on node-1 comes alive
      • start node-2 again
      • check failback of live on node-2
      • when all messages are processed, consume all messages from OutQueue

      Expected result: Receiver gets all messages which were sent.
      Actual result: One or more messages are not delivered into OutQueue. Node-2

      Artemis version: 2.40.0.redhat-00005

              Unassigned Unassigned
              ehugonne1@redhat.com Emmanuel Hugonnet
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: