[
https://issues.apache.org/jira/browse/QPID-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-1637:
---------------------------------
Component/s: Java Broker
Fix Version/s: M5
Description:
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.
Affects Version/s: M4
Remaining Estimate: 8h
Original Estimate: 8h
> 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
> 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:[email protected]
