Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 18 Jan 2013 20:42:12 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12627031.1357853128793.161102.1358541732969@arcas>
In-Reply-To: <JIRA.12627031.1357853128793@arcas>
References: <JIRA.12627031.1357853128793@arcas>
Subject: [jira] [Resolved] (AMQ-4248) FilePendingMessageCursor can retain
 memory after flush to disk till next reset via internal iterator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Tully resolved AMQ-4248.
-----------------------------

    Resolution: Fixed

@Tim thanks.
We may need to revist recursive calls to the cursor on durable sub dispatch.
                
> FilePendingMessageCursor can retain memory after flush to disk till next reset via internal iterator
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4248
>                 URL: https://issues.apache.org/jira/browse/AMQ-4248
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: cursor, memory, oom
>             Fix For: 5.8.0
>
>
> the contract for cursor iteration is to call {code}reset,next...,release{code} 
> If the cursor is flushed on add, the memory list is cleared but the iterator is still referencing the list, which causes memory bloat. It will be released on the next call to reset (which may take some time depending on consumer activity), but it should be gone after the previous call to release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira