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)