[
https://issues.apache.org/jira/browse/ARTEMIS-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790176#comment-17790176
]
ASF subversion and git services commented on ARTEMIS-4506:
----------------------------------------------------------
Commit 60200b44e2d66adecebc2988091ba16bb5aed5a8 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=60200b44e2 ]
ARTEMIS-4506 restore MQTT sub queue name syntax
Starting with 2.28.0, the broker doesn't translate the character `/` to
the configured wildcard delimiter (i.e. `.` by default) when creating
subscription queues for MQTT clients.
This commit fixes that regression and restores the proper translation.
> Restore MQTT subscription queue name syntax
> -------------------------------------------
>
> Key: ARTEMIS-4506
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4506
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Starting with 2.28.0, the broker doesn't translate the character {{/}} to the
> configured wildcard delimiter (i.e. {{.}} by default) when creating
> subscription queues for MQTT clients.
> For example, in previous versions, a client configured with the following
> properties
> {noformat}
> clientId: mqtt
> topic: TEST/TOPIC{noformat}
> would consume message from a queue defined like this:
> {code:xml}
> <addressname="TEST.TOPIC">
> <multicast>
> <queuename="mqtt.TEST.TOPIC"/>
> </multicast>
> </address>{code}
> Now, in the affected versions, this will not work, the client will create (if
> it has permissions to create queues) or will expect (if it doesn't have
> permissions to create queues) a queue with the following format:
> {code:xml}
> <addressname="TEST.TOPIC">
> <multicast>
> <queuename="mqtt.TEST/TOPIC"/>
> </multicast>
> </address>{code}
> This is breaking clients applications when upgrading the broker from
> versions before than 2.28.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
