You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/03/02 17:50:56 UTC
[jira] Assigned: (QPID-1637) Update AMQPriorityQueue, potentially
creating Purger thread
[ https://issues.apache.org/jira/browse/QPID-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1637:
------------------------------------
Assignee: Rob Godfrey (was: Martin Ritchie)
Hi Rob can you review this please.
> Update AMQPriorityQueue, potentially creating Purger thread
> -----------------------------------------------------------
>
> Key: QPID-1637
> URL: https://issues.apache.org/jira/browse/QPID-1637
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Affects Versions: M4
> Reporter: Martin Ritchie
> Assignee: Rob Godfrey
> Fix For: M5
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> The SimpleAMQQueue implementation is easy to decide when to evict a message from memory as all new messages will be at the back of the queue and hence candidates for eviction.
> When a message arrives for a priority queue it is not guaranteed that it can be evicted as it may be high priority and therefore next for delivery. A quick check needs to be performed to calculate if we need to evict the message or at least start an eviction process to find the least important message instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org