Hi Riccardo- The broker stats should help provide clues as to where the messages went. What are the destinations that have enqueue counts? Also, what do you see with consumer counts when the mqtt client connects?
Note on the mqtt w/ virtual topic strategy — the VIrtualTopic config is hard-coded to use VirtualTopic.* and Consumer.*. for the topic and queue prefixes. Also, the mqtt clients connect _without_ the virtual topic prefixes. They connect up with just topic://FOO and then get routed to topic://VirtualTopic.FOO and then the queues.. queue://Consumer.*.VirtualTopic.FOO <queue://Consumer.*.VirtualTopic.FOO>. Hope this helps! -Matt Pavlovich > On Sep 17, 2021, at 5:13 AM, Modanese, Riccardo > <[email protected]> wrote: > > Hi all, > I’m facing a weird behavior when trying to exchange messages between > devices (emulated by clients) connected to different ActiveMQ connectors > (ActiveMQ version 5.14.5). > On one side I have an AMQP device emulated by qpid-jms library. > This device should exchange messages with another one connected through the > MQTT connector. > The messages from AMQP client are published to the broker (I have a custom > security filter and I can log every message published and in which topic) but > don’t flow to the MQTT client. > I’m not sure if the virtual topic feature can be responsible of this. > I tried to publish messages with and without VirtualTopic prefix but without > any success. > > This is the connectors configuration: > > > <transportConnector name="mqtt" > uri="mqtt+nio://0.0.0.0:1883?transport.defaultKeepAlive=60000&transport.maximumConnections=1000&transport.socketBufferSize=131072&transport.ioBufferSize=16384&transport.activeMQSubscriptionPrefetch=32766&transport.publishDollarTopics=true&transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions"/> > > > > <transportConnector > name="amqp"uri="amqp+nio://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=1048576&transport.transformer=jms" > /> > > Any ideas? > > Riccardo
