Hi, I'm exploring the use of mqtt with virtual topics to scale by mqtt subscription fleet.
I was testing with a ws connector and a mqtt connector by having the following transport connectors: <transportConnector name="mqtt+nio" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600&transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions"/> <transportConnector name="mqtt+ws+nio" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600&transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions"/> I noticed that publishing on the mqtt connector (port 1883) successfully pushed messages on to the virtual consumer queues whereas doing the same on the ws connector (port 61614) did not. What could be wrong here? Thanks, baskin -- View this message in context: http://activemq.2283324.n4.nabble.com/mqtt-with-virtual-topics-doesn-t-work-for-websocket-connector-tp4708485.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.