]
Nicolas De Amicis commented on WFLY-13793:
------------------------------------------
I tried the same case under wildfly 20 and it seems that the MDB listen on the right queue
(without jms.queue prefix). The problem was corrected between wildfly 17 and wildfly 20.
Attribute enable-amq1-prefix doesn't work (remote artemis)
----------------------------------------------------------
Key: WFLY-13793
URL:
https://issues.redhat.com/browse/WFLY-13793
Project: WildFly
Issue Type: Bug
Components: JMS, Management
Affects Versions: 17.0.1.Final
Reporter: Nicolas De Amicis
Assignee: Chao Wang
Priority: Major
I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here:
[
https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...]
No problem for point 1 to 3. But when I follow the instruction for disabling the
compatibility mode (enable-amq1-prefix) I have this error:
{quote}{{[standalone@localhost:9990 /]
/subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix",
value="false")}}
\{{{}}
\{{ "outcome" => "failed",}}
\{{ "failure-description" => "WFLYCTL0248: Invalid value false for
enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}}
{{OPIC, TOPIC, QUEUE, XA_QUEUE]",}}
\{{ "rolled-back" => true}}
{{}}}
{quote}
If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is
connected to jms.queue.myqueue.
I also tried to add the attribute manually but it seems it doesn't work:
{quote}{{<pooled-connection-factory name="remote-artemis"
entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis"
enable-amq1-prefix="false"/>}}
{quote}