[
https://issues.apache.org/jira/browse/QPID-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-6299.
------------------------------
Resolution: Fixed
Note: the ring queue discard if required happens before enqueue, the lvq
replacement after it, so where the number of unique keys is less than the ring
size, a new message may cause an old message to be discarded even though the
new message would in fact replace some other message). However this is
considered to be acceptable since both behaviours are arguably honoured, even
if the ring discard is not strictly logically necessary.
> can't combine ring queue and lvq functionality
> ----------------------------------------------
>
> Key: QPID-6299
> URL: https://issues.apache.org/jira/browse/QPID-6299
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.20, 0.22, 0.24, 0.26, 0.28, 0.30
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.31
>
>
> Regression introduced (by me!) in the big refactor after 0.18. If a queue is
> specified to have a ring policy, lvq behaviour won't be supported even if
> requested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
