activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: MQTT Subscriber gets disconnected frequently when there are large number of MQTT clients connected
Date Fri, 27 Oct 2017 12:41:23 GMT
Is there anything in the broker's logs when this happens? I believe the log
content you quoted was from the client, not the broker, and I wasn't sure
if what you wrote meant that there was nothing in the broker's logs, so I
want to make sure.

Can you reproduce the problem in a non-production environment where the use
of a debugger or a profiler or increasing the logging level of the broker
would be an option? Those techniques are the ones that jump to mind for how
to investigate further, starting with increasing the logging level.


On Oct 27, 2017 2:19 AM, "Shobhana" <> wrote:

> 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://;wireFormat.
> maxInactivityDuration=180000&amp;wireFormat.maxFrameSize=
> 104857600&amp;jms.useAsyncSend=true&amp;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:
> f2341805.html

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message