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

Colocated HA topology doesn't work with HTTP connectors and static cluster

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Done
    • None
    • 11.0.0.Alpha1
    • JMS
    • None
    • Hide
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      cd eap-tests-hornetq/scripts/
      git checkout 8c4da4f0ab4ac788ac008a223cde1408a590aff2
      groovy -DEAP_VERSION=7.1.0.DR12 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=ColocatedClusterFailoverTestCase#testFailoverClientAckQueueShutDownStaticConnectors -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 8c4da4f0ab4ac788ac008a223cde1408a590aff2 groovy -DEAP_VERSION=7.1.0.DR12 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=ColocatedClusterFailoverTestCase#testFailoverClientAckQueueShutDownStaticConnectors -DfailIfNoTests= false -Deap=7x | tee log

    Description

      Scenario:

      • 2 EAPs configured in colocated shared store HA topology with HTTP connectors and static cluster
      • static cluster means that cluster-connection is defined by static-connectors property
      • both EAPs and standalone clients are started
      • after that receiver receives 120 messages, first EAP is shut down

      Expectation: Clients do failover to second EAP and continue in their work.
      Reality: Clients are not able to reconnect to backup server.

      During the whole test I see a lot of AMQ214023: HTTP Handshake failed errors.

      The same scenario works with Netty connectors.
      The same scenario works in dedicated topology.

      Priority of this issue is blocker because it is regression against previous versions of EAP 7.1.

      Attachments

        Issue Links

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: