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

Duplicated messages in scenario with stop/start JMS bridge

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 17.0.0.Beta1, 17.0.0.Final
    • 14.0.0.Final
    • JMS
    • None
    • Hide 
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/artifact/jboss-eap.zip -DEAP_ZIP_URL_OLD=http://download.eng.brq.redhat.com/devel/candidates/JBEAP/to_be_deleted/JBEAP-7.1.0/jboss-eap-7.1.0.zip 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 test -Dtest=JMSBridgeTestCase#testStartStopJMSBridge  -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT | tee log
      Show
      git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout eap7.2.x-artemis2.x-ha-jdbc groovy -DEAP_ZIP_URL=https: //mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/artifact/jboss-eap.zip -DEAP_ZIP_URL_OLD=http://download.eng.brq.redhat.com/devel/candidates/JBEAP/to_be_deleted/JBEAP-7.1.0/jboss-eap-7.1.0.zip 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 test -Dtest=JMSBridgeTestCase#testStartStopJMSBridge -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT | tee log

    Description

      There are duplicated messages in scenario where JMS bridge is stopped and started.

      Test Scenario:

      • Start 2 servers and configure JMS from node-1 to node-3
      • Start sending messages to queue InQueue to node-1
      • Stop JMS bridge using management operation (CLI)
      • Wait for 5 sec
      • Start JMS bridge using management operation
      • Start receiving mesage from node-3 from OutQueue

      Expected results:
      There are no lost/duplicated mesages.

      Actual Result:
      Receiver got duplicated messages.

      Link to failed Jenkins run:
      https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-weekly-compatibility-journal-and-jms-bridge/36/EAP_VERSION_OLD=7.1.0.GA,jdk=oracle-java-1.8,os=RHEL7&&large&&dynamic/

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-11606 Upgrade Artemis to 2.6.4

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-11876 Upgrade Artemis to 2.8.0

          • 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

              rhn-support-jbertram Justin Bertram
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: