EAP Resource Adapter for AMQ prefixes queue-names with "jms.queue."

Solution Verified - Updated -

Issue

  • When our Fuse 7.5.0 Camel application puts a message to a queue (eg. .to("amqp:queue:my.queue.123?jmsMessageType=Text&exchangePattern=InOnly")), a queue is created in the remote AMQ Broker 7.4.1 called jms.queue.my.queue.123.
    We expect the queue to be my.queue.123 as specified, without the jms.queue prefix.

Our Fuse runs under EAP and creates the amqp component with a ConnectionFactory defined in EAP's standalone-full-ha.xml file
When we configure our own ConnectionFactory and connect directly to the remote AMQ's AMQP port, the prefix is not added.

Red Hat Jira here suggests that the community WildFly version was modified to expose this via the

  <pooled-connection-factory .... enable-amq1-prefix="false"

attribute but this doesn't appear to be so. EAP doesn't recognize the enable-amq1-prefix attribute.

Please advise how I can stop this prefix being added.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.2.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content