Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <569511263.1241060018113.JavaMail.jira@brutus>
Date: Wed, 29 Apr 2009 19:53:38 -0700 (PDT)
From: "Colin MacNaughton (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2236) activemq-flow: SharedQueue
 cursoring/paging enhancements -- updated queue to enforce a memory limit
 less than the queue's max size
In-Reply-To: <335638546.1241059901320.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-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin MacNaughton updated AMQ-2236:
-----------------------------------

    Attachment: AMQ-2236patch.txt

Patch file.

> activemq-flow: SharedQueue cursoring/paging enhancements -- updated queue to enforce a memory limit less than the queue's max size
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2236
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2236
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: incubation
>         Environment: N/A
>            Reporter: Colin MacNaughton
>             Fix For: incubation
>
>         Attachments: AMQ-2236patch.txt
>
>
> This improvement updates the cursoring logic in shared queue to allow enforcement of a memory limit that is separate from the queue's size limit. If the queue is configured to limit memory then each cursor now additionally gets a memory limiter/controller. When elements are added to the queue open cursors are checked to see if they can absorb the element in memory -- if not the element is paged out to disk. 
> This is still a work in progress -- the implementation is still a bit buggy, and it needs to be further enhanced to throttle back producers to avoid constantly paging out/in elements once the queue's cursors have caught up to the live delivery stream.

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