Details
-
Bug
-
Resolution: Done
-
Blocker
-
8.0.0.Beta-CR1, 8.0.0.Beta
-
None
-
False
-
None
-
False
-
Regression
-
Known Issue
-
Description
EAP with configured messaging-activemq subsystem (Artemis) won't finish the start sequence.
Steps to reproduce (reproducer reproducers the issue in about 90% cases):
git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git cd messaging-testsuite/scripts/ git checkout master groovy -DEAP_ZIP_URL=file:///<path-to-zip>/jboss-eap-8.0.0.Beta-CR1.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 install -B -Dartemis.version=2.21.0 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1669154014-SNAPSHOT -Dmaven.test.failure.ignore=true -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dtest=RemoteBrokerCliAttributesTestCase
Notice BLOCKED thread in thread dump (also attached) and three threads in org.apache.activemq.artemis.utils.JsonLoader.readArray method suggesting a race condition.
Customer impact: In case of running full and full-ha profile (messaging-activemq subsystem is present), it can happen that server does not fully start.
