I think I see now, but I want to confirm since I've not seen this kind of configuration before. You've intentionally configured 2 federation connections in a redundant fashion so that each connection is sending the same message resulting in duplicates on the target. Is that correct?
Are you using pub/sub in your OpenWire use-case? Also, can you share your federation config from broker.xml? Justin On Wed, Jun 11, 2025 at 3:18 AM Devriendt, Erik <erik.devrie...@siemens.com.invalid> wrote: > > > > 1) The MQTT specification didn't even support message properties until 5. > > > 2) The MQTT specification already has a way to deal with duplicates > using its quality-of-service levels. > > > > > > Is there a use-case where using _AMQ_DUPL_ID would be preferred over > using, for example, QoS 2? > > > > In my setup, QoS 2 does not prevent receiving the messages twice. > > > > > > MQTT client/publisher --> Artemis1 <--federation-conn1--> Artemis2 -> MQTT > client/subscriber > > \ / > > \--federation-conn2--/ > > > > Both federation-conn are up in parallel. > > > > However, with the same Artemis1/2 setup, but Openwire (CMS) publisher and > subscriber, the subscriber only gets the message once, > > Artemis2 reports reception of duplicate message, and drops it. >
