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

Shutdown of server with remote JCA MDB may take too long

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.2.3.CR1, 7.2.3.GA
    • 7.1.0.CR1, 7.1.0.CR4, 7.2.0.CD12, 7.2.0.GA
    • ActiveMQ
    • 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

      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.

        1. standalone-full-ha.xml
          37 kB
        2. thread-dump.html
          2.51 MB

              rhn-support-iweiss Ingo Weiss
              okalman@redhat.com Ondřej Kalman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: