activemq-issues mailing list archives

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


Michael Feingold commented on AMQ-5762:

Yep. We built a test harness off of the example based on the fusesource client. It is really
straightforward - it creates a thousand connections and then cycles through closing them and
opening them. We ran this test overnight several times on different versions of AMQ. After
a 100 of cycles the memory heap was at 7Gb after the manually triggered GC. We also tested
the hard close by killing the client app and restarting it as well as cutting off network
by playing with firewall settings. This is where we got the 300K per close. We ran all of
this on the out of the box AMQ config. The only change was we turned on thread pooling and
configure nio

I would be happy to share the test harness if it would help any.

> 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
>            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