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

[QA](7.4.z) ENTMQBR-5385 - Different number of large messages between queues when using bridge

    XMLWordPrintable

Details

    • False
    • False
    • +
    • Undefined
    • Hide 
      git clone git@gitlab.hosts.mwqe.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git

export EAP_ZIP_URL=file:///<PATH>/jboss-eap-7.4.0.GA-CR2.zip
export EAP_VERSION=7.1623836938-SNAPSHOT

cd messaging-testsuite
export WORKSPACE=$PWD

echo "use groovy-2.2.1"
groovy scripts/PrepareServers7.groovy
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
mkdir journal_A
mkdir journal_B
export JOURNAL_DIRECTORY_A=$WORKSPACE/journal_A
export JOURNAL_DIRECTORY_B=$WORKSPACE/journal_B

cd jboss-hornetq-testsuite

mvn clean install -B -Dartemis.version=2.16.0 -Dartemis.version=2.16.0 -DexcludedGroups=None,category.scope.Broker -Dgroups=category.Bridge -Dsurefire.timeout=93600 -Deap7.org.jboss.qa.hornetq.apps.clients.version=$EAP_VERSION -DreuseForks=false -Dmaven.test.failure.ignore=true -Deap7.clients.version=$EAP_VERSION -Dtest=CoreBridgeOOMEAndCpuLoadTestCase#testCpuLoadOnTargetServer
      Show
      git clone git@gitlab.hosts.mwqe.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git export EAP_ZIP_URL=file:///<PATH>/jboss-eap-7.4.0.GA-CR2.zip export EAP_VERSION=7.1623836938-SNAPSHOT cd messaging-testsuite export WORKSPACE=$PWD echo "use groovy-2.2.1" groovy scripts/PrepareServers7.groovy 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 mkdir journal_A mkdir journal_B export JOURNAL_DIRECTORY_A=$WORKSPACE/journal_A export JOURNAL_DIRECTORY_B=$WORKSPACE/journal_B cd jboss-hornetq-testsuite mvn clean install -B -Dartemis.version=2.16.0 -Dartemis.version=2.16.0 -DexcludedGroups=None,category.scope.Broker -Dgroups=category.Bridge -Dsurefire.timeout=93600 -Deap7.org.jboss.qa.hornetq.apps.clients.version=$EAP_VERSION -DreuseForks=false -Dmaven.test.failure.ignore=true -Deap7.clients.version=$EAP_VERSION -Dtest=CoreBridgeOOMEAndCpuLoadTestCase#testCpuLoadOnTargetServer

    Description

      In the following scenario:

      • Start two EAP 7.x servers (node 1 and 2).
      • Configure Core bridge from InQueue (node 1) to OutQueue (node 2).
      • Send 5000 messages into InQueue (node 1) and cause 5 min 100% CPU load on target server (node 2).
      • Once 100% CPU load finishes consume messages from OutQueue (node 2)
      • receiver reads same amount of messages as was sent to source server of core bridge

      we observe the following error:

      There is different number of sent and received messages. expected:<5000> but was:<5377>

      This is not a regression: it's reproducible with EAP 7.3.8.GA;

      Test logs in attached complete-logs.zip;

      Complete CI Run here;

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-5385 [LTS] Duplicated messages with bridge duplicate detection enabled

          • 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.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-22226 [RN] Different number of large messages between queues when using bridge

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-21308 (7.4.z) Upgrade Artemis from 2.16.0.redhat-00022 to 2.16.0.redhat-00032

          • 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
          links to

          Web Link Apache Artemis Issue

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              tborgato@redhat.com Tommaso Borgato
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: