configuration file instead of the level where it (and all others)
> belong.
> Thus the settings were ignored.
> Works as expected now.
>
> Thx!
> e.
>
> -Original Message-
> From: Justin Bertram
> Sent: donderdag 6 juli 2023 05:20
> To: users@acti
@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
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
wrote:
> Hello,
>
> I have an MQTT3 client that publishes messages to the Artemis broker on
>
If you are using JMS and topic subscriptions the queue name may be
different between the two implementations.
You could use FQQN in AMQP to match the queue used in MQTT.
On Tue, Jul 4, 2023 at 12:59 PM Dondorp, Erwin
wrote:
> Hello,
>
> I have an MQTT3 client that publishes messages to the
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
'/' is applied.
Therefore I would have expected the address
