Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-105

[RFE EAP7-1014] Pooled connection factory with discovery group doesn't work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • Artemis, JMS
    • None
    • Hide

      Build wildfly from https://github.com/ehsavoie/wildfly/tree/WFLY-10518_artemis_no_local_broker

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
git checkout EAP7-1014
cd eap-tests-hornetq/scripts/
groovy -DEAP_ZIP_URL=<PATH_TO_BUILD_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=RemoteBrokerTestCase#testPooledConnectionFactoryWithDiscoveryGroup | tee log
      Show
      Build wildfly from https://github.com/ehsavoie/wildfly/tree/WFLY-10518_artemis_no_local_broker git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git git checkout EAP7-1014 cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=<PATH_TO_BUILD_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=RemoteBrokerTestCase#testPooledConnectionFactoryWithDiscoveryGroup | tee log

      Scenario:
      Node1 w/o Artemis server has PCF with discovery group

      <subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
       <discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster"/>
       <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" discovery-group="dg-group1" transaction="xa"/>
       <external-jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue"/>
       <external-jms-queue name="OutQueue" entries="jms/queue/OutQueue java:jboss/exported/jms/queue/OutQueue"/>
</subsystem>

      Node2 w/ Artemis server has broadcast group 

      <server>
          <broadcast-group name="bg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" connectors="connector"/>
          <http-connector name="connector" socket-binding="http" endpoint="acceptor"/>
          <http-acceptor name="acceptor" http-listener="default"/>
          <jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/>
          <jms-queue name="OutQueue" entries="jms/queue/OutQueue java:jboss/exported/jms/queue/OutQueue" durable="true"/>
          ....
</server>

      For full configuration please see attached xmls.

      MDB is deployed to Node1. It should use RA(PCF) to read messages from node2. However it can not connect.

          15:51:51,738 ERROR [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ154003: Unable to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter@64121323 destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster]
            at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:749) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
            at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:311) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
            at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.reconnect(ActiveMQActivation.java:658) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
            at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:698) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
            at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
            at org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
            at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
            at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
            at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
            at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
            at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
            at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
            at org.jboss.threads.JBossThread.run(JBossThread.java:485)

      Same scenario works with connectors. This is blocker EAP7-1014.

        1. standalone-full-ha-node1.xml
          34 kB
        2. standalone-full-ha-node2.xml
          40 kB

              ehugonne1@redhat.com Emmanuel Hugonnet
              mstyk_jira Martin Styk (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: