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

Shutdown of server with remote JCA MDB may take too long

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Critical
    • None
    • AMQ 7.2.1.GA
    • broker-core
    • None
    • Hide

      Steps to reproduce:

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout master

groovy -DEAP_ZIP_URL=http://download.eng.brq.redhat.com/released/JBEAP-7/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=RemoteJcaTestCase#testCleanShutDownOfMdbServer    -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1.0.CR4 -DfailIfNoTests=false -B | tee log
      Show
      Steps to reproduce: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout master groovy -DEAP_ZIP_URL=http: //download.eng.brq.redhat.com/released/JBEAP-7/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=RemoteJcaTestCase#testCleanShutDownOfMdbServer -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1.0.CR4 -DfailIfNoTests= false -B | tee log
    • AMQ Sprint 3219, AMQ Broker 1119

    Description

      We have following scenario:
      EAP has configured pooled-connection-factory to use discovery-group to create remote JCA connection and we have one MDB deployed on it. When there are no broadcasting nodes in this group and we try to shut down a server early it may happen that ActiveMQActivation.setup() is still running and trying to create sessions for MDB. Each attempt of creation this session will take by default 10 seconds and there will be by default about 10 attempts to create the session. This loop will hold server shutdown for a significant amount of time, by default it's about 2 minutes but it may be longer if MDB is configured with "maxSession" attribute to a higher value.

      I think that Artemis should at least log some information about what is happening and how long it will take.

      I'll note that there used jgroups tcp stack (with static nodes) in configuration of discovery group.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12983 Shutdown of server with remote JCA MDB may take too long

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2029 [ARTEMIS-2105] Discovery group connectors can delay broker shutdown

          • 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
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. WFWIP-88 [Artemis 2.x upgrade] Server shutdown hangs with active MDB

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: