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

Connection Timeout now blocks on the retry, it should be asynchronous

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • AMQ 7.4.1.GA
    • AMQ 7.4.0.GA
    • None
    • None
    • ARTEMIS-2440
    • Hide 
      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git
cd messaging-testsuite/scripts/
git checkout eap7.2.x

groovy -DEAP_ZIP_URL=https://eap-cp-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-72x-messaging-testing-prepare/30/artifact/jboss-eap.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=RemoteJcaTestCase#testShutdownOfMdbWhenJmsServerIsDown -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1564326398-mackaypeter-artemis_290-SNAPSHOT | tee log
      Show
      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git cd messaging-testsuite/scripts/ git checkout eap7.2.x groovy -DEAP_ZIP_URL=https: //eap-cp-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-72x-messaging-testing-prepare/30/artifact/jboss-eap.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=RemoteJcaTestCase#testShutdownOfMdbWhenJmsServerIsDown -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1564326398-mackaypeter-artemis_290-SNAPSHOT | tee log

      We have following scenario:

      • 2 EAP instances (nodeA, nodeB)
      • nodeB has a MDB deployed, that consumes messages from an InQueue on nodeA and resends them to an OutQueue also on nodeA
      • during the MDB processing of messages, nodeA is killed (actually killed, not a clean shutdown)

      After that nodeB hangs when trying to shut it down and has to be killed.
      This is a regression against 7.2.3.CR2 with Artemis 2.7.0.redhat-00057

        1. node-2-thread-dump-before-kill-shutdown-sequence.txt
          247 kB
        2. node-2-thread-dump-when-killed-shutdown-sequence.txt
          247 kB
        3. server-trace.log
          47.24 MB

              csuconic@redhat.com Clebert Suconic
              ehugonne1@redhat.com Emmanuel Hugonnet
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: