[
https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818820#comment-15818820
]
Rob Godfrey commented on QPID-7618:
-----------------------------------
I'm not sure this code in AbstractQueueEntryList is safe in the face of a
message which is in itself bigger than the max queue size limit - I think it
would probably NullPointerException (this.getOldestEntry() returning null) or
else loop infinitely
{code}
while (getQueue().getQueueDepthBytesIncludingHeader() +
message.getSizeIncludingHeader() > _queue.getMaxSize())
{
QueueEntry entry = this.getOldestEntry();
if (entry.acquire())
{
entry.delete();
}
}
{code}
> Ring policy type
> ----------------
>
> Key: QPID-7618
> URL: https://issues.apache.org/jira/browse/QPID-7618
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: qpid-java-6.1.1, qpid-java-7.0
> Reporter: Tomas Vavricka
> Labels: policy-type, queue, ring
> Attachments: 0001-QPID-7569-Ring-policy-type.patch
>
>
> It would be good if Java Broker will support ring policy.
> Ring policy - delete oldest message(s) when queue capacity is reached
> Queue capacity can be defined by maximum count of message and maximum size of
> messages (including header).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
