Antwort: [Ext] ActiveMQ Classic: NIO or TCP?

Hello Endre, to my experience nio on the broker is absolutely cool.. It is faster and decoupling clients. On the client side it makes no difference. Regards Herbert Von:"Endre Stølsvik" An: users@activemq.apache.org Datum: 29.08.2023 13:47 Betreff:[Ext] ActiveMQ Classic: N

Re: Messages balance between two MQTT connections open with same clientId on different acceptors

> if the "clientB" tries to connect to another acceptor (not the same one used by the "clientA"): it won't be able to connect, regardless of the stealing link configuration That is not correct. If "clientB" tries to connect to another acceptor (not the same one used by the "clientA") then the link

ActiveMQ Classic: NIO or TCP?

Hi! Wrt. TransportConnectors: What is the general recommendation? Is NIO better than TCP? Or the other way around? I do get the obvious points wrt. threads - but it also depends on the implementation, and real-life experiences wrt. throughput and latency. Thanks a lot, Kind regards Endre

R: Messages balance between two MQTT connections open with same clientId on different acceptors

Hi Justin, thanks for your reply. If I got it right, the stealing link configuration will remain at acceptor level. Then, given an MQTT client "clientA" connected to the broker with the clientId "testClientId", and another MQTT client "clientB" wanting to connect to the broker with the same cli