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

Messages are stuck in sf queue when core-bride is disconnected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • 7.0.0.ER2 (Beta), 7.0.0.ER6, 7.1.0.DR19
    • ActiveMQ
    • None
    • Hide

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git

      cd eap-tests-hornetq/scripts/

      git checkout refactoring_modules

      groovy -DEAP_VERSION=7.0.0.ER2 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

      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 test -Dtest=NetworkFailuresHornetQCoreBridges#testNetworkFailureSmallMessages1recAttempts -DfailIfNoTests=false -Deap=7x | tee log

      Show
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout refactoring_modules groovy -DEAP_VERSION=7.0.0.ER2 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 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 test -Dtest=NetworkFailuresHornetQCoreBridges#testNetworkFailureSmallMessages1recAttempts -DfailIfNoTests=false -Deap=7x | tee log

      Scenario:
      1) Two Artemis servers are running in cluster
      2) On cluster connection is set <reconnect-attempts>1</reconnect-attempts>
      3) Messages are sent to input queue on Node 1 and read from Node 2
      4) Network failure is executed
      5) Cluster fails to reconnect, one reconnect attempt is not enough because of network failure duration
      6) We wait some time until all messages (2 minutes) from Node 2 are consumed and then shut it down
      7) Then we restart Node 1 and consume all messages which was not transferred to Node 2 from input queue.

      Expected:
      Number of sent messages should be equal to sum of consumed messages from Node 1 and Node 2.
      All undelivered messages between cluster nodes should be immediately transferred back to input queue when maximum reconnect-attempts is reached and and connection is not established.

      Actual:
      Number of sent messages doesn't equal to sum of consumed messages from Node 1 and Node 2. In queue which was created for clustering purpose are undelivered messages, waiting for cluster to reconnect.

              rhn-support-jbertram Justin Bertram
              okalman@redhat.com Ondřej Kalman (Inactive)
              Ondřej Kalman Ondřej Kalman (Inactive)
              Ondřej Kalman Ondřej Kalman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: