4 Replies Latest reply on May 24, 2019 3:16 AM by ehugonnet

    A jms.queue Prefix Added When Accessing Remote Artemis with Wildfly 16 Embedded Adapter

    Felipe Fraga Newbie

      Hello all,


      I have configured the messaging subsystem on a Wildly 16 to connect to a remote ActiveMQ Artemis 2.6.4 using the embedded resource adapter. Queues are automatically created on demand.


      I am able to connect and receive messages, but a jms.queue prefix is added to every queue created. I assume that this is because and old HornetQ or Artemis 1.x client is being used instead of the Artemis client. Is that correct? Can I do anything about it? Here is my relevant snippets:


      <remote-connector name="remote-artemis" socket-binding="remote-artemis"/>

      <jms-queue name="ExampleQueue" entries="java:/jms/queue/ExampleQueue"/>

      <pooled-connection-factory name="remote-artemis" entries="java:/jms/remoteCF" connectors="remote-artemis" user="user" password="pass" transaction="xa"/>

      <outbound-socket-binding name="remote-artemis">

          <remote-destination host="localhost" port="61616"/>



      And on my producer:




          private JMSContext context;



          private Queue queue;


      This configuration will create a queue called jms.queue.ExampleQueue instead of simply ExampleQueue. Can anyone point what I am doing wrong?


      Thanks in advance.