[
https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882398#comment-15882398
]
Lorenz Quack commented on QPID-7618:
------------------------------------
As discussed in private I think the fix for the threading issue mentioned above
is more complicated than necessary.
I think instead of checking for underfull condition in
{{ProducerFlowControlOverflowPolicyHandler.Handler#checkOverfull}} we should
remove the {{if (_overfull.get())}} in
{{ProducerFlowControlOverflowPolicyHandler.Handler#checkUnderfull}}. Then the
{{_overfull}} field should be renamed to something like {{_overfullReported}}.
> 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
> Fix For: qpid-java-7.0
>
> Attachments: 0001-QPID-7569-Ring-policy-type.patch,
> overflow-policy.tar.gz
>
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
