Background : We use AMQ to exchange MQTT non-persistent messages between our server components and clients (Android/iOS devices). About 100-200 messages/second get exchanged during peak hours.
This is our MQTT transport connector configuration : <transportConnector name="mqtt+nio" uri="mqtt+nio://0.0.0.0:1883?maximumConnections=200000&wireFormat.maxInactivityDuration=180000&wireFormat.maxFrameSize=104857600&jms.useAsyncSend=true&jms.alwaysSessionAsync=false"/> When there are more than 10000 MQTT connections (and roughly about 30000 topics), the MQTT subscribers get disconnected. Even publish operations time out (timeout is set to 60 seconds on the publisher and subscriber end). After a few attempts, connection gets re-established. Once broker enters this state, disconnects become more frequent and after sometime, the reconnect also fails forever until the broker is restarted! Any suggestions on how to investigate why this happens? Since this is a production environment, I can't debug/profile the broker. I have checked memory usage and CPU usage .. both are well under control. Thread dumps show that there are no blocked threads. Log level is set to WARN only. Sometimes I see following error in log files when this happens : Any clue about what is happening or how to investigate further? TIA, Regards, Shobhana -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
