[
https://issues.jboss.org/browse/WFLY-10055?page=com.atlassian.jira.plugin...
]
Jeff Mesnil commented on WFLY-10055:
------------------------------------
[~martyn-taylor] this one should go in your backlog, right?
One solution would be to configure the JMS connection-factory so that it adds prefix to
destinations created on the client side.
However, for backwards compatibility, there might be 4 different types of prefix iirc
(jms.queue, jms.topic, jms.tempqueue and jms.temptopic).
[Artemis 2.x Upgrade] Auto-create-queue creates runtime queue
without jms.queue prefix
---------------------------------------------------------------------------------------
Key: WFLY-10055
URL:
https://issues.jboss.org/browse/WFLY-10055
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Martin Styk
Assignee: Martyn Taylor
{{Auto-create-jms-queue}} feature of EAP 7.1 creates runtime queues with name pattern
{{"jms.queue.<QUEUE_NAME>"}}.
With Artemis 2.5, {{auto-create-queue}} is a successor of deprecated
{{auto-create-jms-queue}} feature. {{Auto-create-queue}} creates queues with name pattern
{{"<QUEUE_NAME>"}}.
{code}
session.createQueue("testQueue")
--> "jms.queue.testQueue" (EAP 7.1 + Artemis 1.5,
auto-create-jms-queue=true)
--> "testQueue" (Artemis 2.5, auto-create-queue=true)
{code}
This feature is not supported.
Issue was hit with Artemis 2.5.0 with
https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w...
(commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)