Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13793

Allow for a remote jms queue / topic not to use legacy amq1 prefix

    XMLWordPrintable

Details

    Description

      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-connection-factory_to_a_Remote_Artemis_Server 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:

      [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}}
      }

      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:

      <pooled-connection-factory name="remote-artemis" entries="java:/jms/remoteCF" connectors="remote-artemis" enable-amq1-prefix="false"/>

      Attachments

        Issue Links

          Activity

            People

              chaowan@redhat.com Chao Wang
              deamn Nicolas De Amicis
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: