Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <2037745030.1245084995408.JavaMail.jira@brutus>
Date: Mon, 15 Jun 2009 09:56:35 -0700 (PDT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2290) Memory leak in SelectorParser LRUCache
In-Reply-To: <1841700604.1245083075528.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-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52265#action_52265 ] 

Gary Tully commented on AMQ-2290:
---------------------------------

does the 80 in that screenshot indicate the number of LRUCache instances? If so, what container are you running. There must be a bunch of classloaders in the mix that can result in multiple instances of that static member.


> Memory leak in SelectorParser LRUCache
> --------------------------------------
>
>                 Key: AMQ-2290
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2290
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Selector
>    Affects Versions: 5.3.0
>            Reporter: Chetan Sarva
>         Attachments: selectorparser-leak.png
>
>
> There appears to be a memory leak in the LRUCache used by the SelectorParser. We have a simple selector-based request/response implementation which means we create a new selector on every request and these appear to be sticking around despite the use of an LRUCache with a 10,000 entry limit. A quick look at the LRUCache code didn't reveal any obvious problems, so I'm not sure what's going on here. For the time being we are rolling back to 5.2. 

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