Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F34DF17C87 for ; Thu, 14 May 2015 20:24:59 +0000 (UTC) Received: (qmail 2720 invoked by uid 500); 14 May 2015 20:24:59 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 2693 invoked by uid 500); 14 May 2015 20:24:59 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 2683 invoked by uid 99); 14 May 2015 20:24:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2015 20:24:59 +0000 Date: Thu, 14 May 2015 20:24:59 +0000 (UTC) From: "Timothy Bish (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-5762) Severe memory leak in the MQTT connector MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544306#comment-14544306 ] Timothy Bish commented on AMQ-5762: ----------------------------------- I've found the issue already, and have a patch going in soon. I will let you know once I've finished testing and added committed the fix, you can then pull down the latest source from github and build or you can wait until a new SNAPSHOT build is done and run against that. > 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, Screen Shot 2015-05-14 at 2.06.02 PM.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)