Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <811038021.1223474274564.JavaMail.jira@brutus>
Date: Wed, 8 Oct 2008 06:57:54 -0700 (PDT)
From: "Aaron Pieper (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-1889) Usage leak in broker when subscribing to
 a topic using selector
In-Reply-To: <875724979.1218809153283.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aaron Pieper updated AMQ-1889:
------------------------------

    Attachment: BrokerMemoryLeak.java

This test case demonstrates a memory leak in the Broker Service. When you execute it, BrokerService's memory percent steadily increases until it hits 100. Then, messages stop being sent.

Originally posted to the mailing list: http://www.nabble.com/Memory-leak-in-broker-when-subscribing-to-a-topic-using-TCP-connector-%2B-noLocal--td18821110.html

> Usage leak in broker when subscribing to a topic using selector
> ---------------------------------------------------------------
>
>                 Key: AMQ-1889
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1889
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.1.0
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 5.2.0
>
>         Attachments: BrokerMemoryLeak.java
>
>
> Original reported in [the mailing list|http://www.nabble.com/Memory-leak-in-broker-when-subscribing-to-a-topic-using-TCP-connector-%2B-noLocal--tp18821110p18821110.html]
> Original report notices the problem with noLocal, but I belive that the usage leak when any selector is used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.