[
https://issues.apache.org/jira/browse/ARTEMIS-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915897#comment-16915897
]
Justin Bertram edited comment on ARTEMIS-2455 at 8/30/19 7:09 PM:
------------------------------------------------------------------
Thank you, I was thinking that the wildcard address configuration changes only
the CORE protocol settings since MQTT protocol has its own well known wildcards.
With this configuration it works
{code:xml}
<wildcard-addresses>
<routing-enabled>true</routing-enabled>
<delimiter>.</delimiter>
<any-words>#</any-words>
<single-word>*</single-word>
</wildcard-addresses>
{code}
But what about multiple protocols on the same (and/or different) acceptors?
For example what happens if I keep this wildcard address configuration and I’ll
have one acceptor with MQTT protocol and one acceptor with CORE protocol?
In other word, I need to keep multiple acceptor with specific (and different)
protocols supported and keep them compatible with their wildcards syntax.
Is there a way to achieve that (since I suppose that the current wildcard
syntax will affect also the CORE protocol handling)?
was (Author: [email protected]):
Thank you, I was thinking that the wildcard address configuration changes only
the CORE protocol settings since MQTT protocol has its own well known wildcards.
With this configuration it works
<wildcard-addresses>
<routing-enabled>true</routing-enabled>
<delimiter>.</delimiter>
<any-words>#</any-words>
<single-word>*</single-word>
</wildcard-addresses>
But what about multiple protocols on the same (and/or different) acceptors?
For example what happens if I keep this wildcard address configuration and I’ll
have one acceptor with MQTT protocol and one acceptor with CORE protocol?
In other word, I need to keep multiple acceptor with specific (and different)
protocols supported and keep them compatible with their wildcards syntax.
Is there a way to achieve that (since I suppose that the current wildcard
syntax will affect also the CORE protocol handling)?
> Unexpected MQTT path separator conversion handling
> --------------------------------------------------
>
> Key: ARTEMIS-2455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2455
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
> Affects Versions: 2.9.0
> Reporter: Riccardo Modanese
> Priority: Minor
> Attachments: MqttTopicIT.java
>
>
> Hello, I noticed an unexpected MQTT path separator conversion handling. (May
> be I'm missing some configuration parameter in the acceptor definition?)
> The char '.' on a MQTT topic is handled by Artemis as a topic separator
> instead of a "normal" topic character. So an MQTT topic like 'a.b.c.d'
> becames 'a/b/c/d'.
> I attach a Junit test I developed for testing different topics.
> I used Artemis 2.9.0. The acceptor configuration is:
> {{tcp://0.0.0.0:1883?tcpSendBufferSize=1048576&tcpReceiveBufferSize=1048576&protocols=MQTT&allowLinkStealing=true&useEpoll=true}}
>
> Regards,
> Riccardo
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
