activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Feingold (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5762) Severe memory leak in the MQTT connector
Date Tue, 12 May 2015 19:01:00 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540489#comment-14540489
] 

Michael Feingold commented on AMQ-5762:
---------------------------------------

I looks like we can consistently reproduce the memory leak in a variety of environments AMQ
versions and configuration options.

A stupid though just occurred to me - when you were running my MQTTBatchDisconnect test -
did you take it from github as is? If it so, the test was only running connect/disconnect
scenario. On clean install thus scenario does not leak. 

My initial intent was to run the test from a command line with parameters, but then I grew
lazy and set parameters directly in the code, currently in line 12. The checked in version
of the test sets the QoS to "none", so there is no call to subscribe during the test. The
test runs with the leak have the second parameter set to "2". I will modify the code in the
repo for your convinience

> Severe memory leak in the MQTT connector
> ----------------------------------------
>
>                 Key: AMQ-5762
>                 URL: https://issues.apache.org/jira/browse/AMQ-5762
>             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
>         Attachments: Screen Shot 2015-05-12 at 20.06.47.png, activemq.xml, wrapper.conf
>
>
> 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
(v6.3.4#6332)

Mime
View raw message