Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 825C0115EB for ; Tue, 8 Jul 2014 00:19:34 +0000 (UTC) Received: (qmail 40582 invoked by uid 500); 8 Jul 2014 00:19:34 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 40525 invoked by uid 500); 8 Jul 2014 00:19:34 -0000 Mailing-List: contact dev-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 dev@activemq.apache.org Received: (qmail 40511 invoked by uid 99); 8 Jul 2014 00:19:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 00:19:34 +0000 Date: Tue, 8 Jul 2014 00:19:34 +0000 (UTC) From: "Aravind Chennuru (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-5261) Memory leak in ActiveMQ JMX objects 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-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravind Chennuru updated AMQ-5261: ---------------------------------- Attachment: 1ConsumerMultipleProducers.png > Memory leak in ActiveMQ JMX objects > ----------------------------------- > > Key: AMQ-5261 > URL: https://issues.apache.org/jira/browse/AMQ-5261 > Project: ActiveMQ > Issue Type: Bug > Components: JMX > Affects Versions: 5.9.0 > Environment: Windows and Solaris > Reporter: Aravind Chennuru > Priority: Critical > Attachments: 1ConsumerMultipleProducers.png, ActiveMQJMXObjects.png, BrokerOOM.png, activemq-jmx-leak.zip > > > Starting from 5.9.0 version of ActiveMQ we seem to have a memory leak in the JMX objects which seems to be causing OutOfMemory in this process. -- This message was sent by Atlassian JIRA (v6.2#6252)