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

[felipefraga]

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"/>

</outbound-socket-binding>

And on my producer:

    @Inject

    @JMSConnectionFactory("jms/remoteCF")

    private JMSContext context;

    @Resource(lookup="java:/jms/queue/ExampleQueue")

    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.

[ehugonnet]

For retro compatibility we add the jms.queue prefix in queue name for WildFly.

You can control this by setting the property enable1xPrefixes to false in the resource adapter.

[felipefraga]

Like a charm. Thanks!

I am having issues now connecting to a 2.6.4 Artemis from a legacy 1.5.5 (a.k.a Wildfly-13 embedded Artemis) but I will ask it in another thread.

Thanks again. =)

[stga1970]

Which configuration did you changed to add the property "enable1xPrefixes"?

[ehugonnet]

This has been exposed in WildFly 17 [WFLY-12038] Expose the enable1Prefixes configuration on external (pooled) connection factories - JBoss Issue Tracker