Justin, You are right. I had placed the <wildcard-addresses> at the <configuration> level in the configuration file instead of the <core> level where it (and all others) belong. Thus the settings were ignored. Works as expected now.
Thx! e. -----Original Message----- From: Justin Bertram <jbert...@apache.org> Sent: donderdag 6 juli 2023 05:20 To: users@activemq.apache.org Subject: Re: mixing MQTT and AMQP EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. I would say this is not expected. I just tested this on main and it worked fine. The broker used '/' instead of '.'. Do you have a reproducer? Justin On Tue, Jul 4, 2023, 11:59 AM Dondorp, Erwin <erwin.dond...@cgi.com.invalid> wrote: > Hello, > > I have an MQTT3 client that publishes messages to the Artemis broker > on topic/address 'aaa/bbb/ccc'. > In the Artemis broker, the messages show up under address 'aaa.bbb.ccc'. > That address is surprising since the setting > '<wildcard-addresses><delimiter>/</delimiter></wildcard-addresses>' is > applied. > Therefore I would have expected the address 'aaa/bbb/ccc' to be used. > > Is this the expected behaviour? > > Btw, for MQTT-->MQTT scenario's this still works fine, as both > publisher and subscriber use the same logic. > But a MQTT-->AMQP scenario fails because it is a different address. > > thx, > Erwin >
