Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Component/s: JMS
    • Labels:
      None
    • Steps to Reproduce:
      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 EAP7-1006
      
      groovy -DEAP_ZIP_URL=file:///<path_to_wf_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#testConnectionFactoryDefinitionToRemoteBroker    -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.GA.CR1 | 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 EAP7-1006 groovy -DEAP_ZIP_URL=file: ///<path_to_wf_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#testConnectionFactoryDefinitionToRemoteBroker -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.GA.CR1 | tee log

      Description

      JMS Destination is not created on remote broker/cluster if activemq-ra resource adapter is configured to connect to it.

      Test scenario:

      • Start two servers in Artemis cluster (node-1, node-3)
      • Start one more server (node-2) which has configured activemq-ra with initial connectors to remote cluster (node-1, node-3)
      • Deploy MDB with to node-2 with:
        @JMSConnectionFactoryDefinition(
                name="java:/jms/myRemoteJmsCf",
                resourceAdapter="activemq-ra")
        
        @JMSDestinationDefinitions({
                @JMSDestinationDefinition(
                        name = "java:/jms/queue/myRemoteOutQueue",
                        interfaceName = "javax.jms.Queue",
                        resourceAdapter = "activemq-ra",
                        destinationName = "myRemoteOutQueue"),
                @JMSDestinationDefinition(
                        name = "java:/jms/queue/myRemoteInQueue",
                        interfaceName = "javax.jms.Queue",
                        resourceAdapter = "activemq-ra",
                        destinationName = "myRemoteInQueue")
        })
        
        • MDB resends messages from myRemoteInQueue to myRemoteOutQueue (send using java:/jms/myRemoteJmsCf)
      • Deploy Servlet to node-2 which uses myRemoteJmsCf to send messages to myRemoteInQueue which are then processed by MDB and re-sent to myRemoteOutQueue

      Expected result: All messages will be in myRemoteOutQueue

      Actual result: No message was processed

      Investigation:
      Problem is that both of the queues were created on node-2 and not in remote artemis cluster (node-1,3)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ehugonnet Emmanuel Hugonnet
                Reporter:
                mnovak Miroslav Novak
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: