activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-5762) Severe memory leak in the MQTT connector
Date Tue, 05 May 2015 22:20:00 GMT


Timothy Bish commented on AMQ-5762:

Just sharing some thoughts based on initial look at the repo which is a little cluttered so
I wasn't 100% sure what all was under test.  Would be nice to reduce the test to the simplest
possible reproducer.  I created a simple unit test based on what I thought the code was attempting
to do and did some profiling and didn't see anything that was surprising.  For a test case
where the subscriptions are not durable and the broker had been configured to GC inactive
destinations my memory remained fairly stable although it did look as though the MQTT FuseSource
client was retaining memory for closed connections.  You might want to give the Paho MQTT
client a shot in your testing.  

> Severe memory leak in the MQTT connector
> ----------------------------------------
>                 Key: AMQ-5762
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.10.1, 5.10.2, 5.11.0, 5.11.1
>            Reporter: Michael Feingold
>            Assignee: Timothy Bish
>            Priority: Critical
> When an MQTT connection is closed some memory is not released. In case of the soft close
(calling connection close on the client) memory leaks at the rate of 70K per connection close.
In case of the hard close (pulling the wire, or cutting off the network connection) the leak
goes at the rate of 300K per close. we also checked it on version 5.11 - same problem

This message was sent by Atlassian JIRA

View raw message