You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Aaron Pieper (JIRA)" <ji...@apache.org> on 2008/10/08 15:57:54 UTC
[jira] Updated: (AMQ-1889) Usage leak in broker when subscribing to
a topic using selector
[ 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.