[ 
https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887841#comment-15887841
 ] 

ASF subversion and git services commented on QPID-7618:
-------------------------------------------------------

Commit 1784725 from [email protected] in branch 'java/trunk'
[ https://svn.apache.org/r1784725 ]

QPID-7618: Address review comments from Keith Wall and fix remaining issues

* Fix upgrader functionality to use correct overlow policy name
  for 'producer flow control'
* Use attribute 'queueDepthBytesIncludingHeader' instead of attribute
  'queueDepthBytes' in producer flow control handler
* Fix UI for queue editing to stop displaying error message
  when overflow policy is not set explicitly
* On queue UI display 'unlimited' for negative queue depth limit values
* Rename methods #getLesserOldestEntry into #getLeastSignificantOldestEntry
* Change SortedQueueEntryList to return the oldest entry from
  QueueEntryList#getLeastSignificantOldestEntry
* Remove redundant code in
  ProducerFlowControlOverflowPolicyHandler.Handler#bulkChangeEnd
  mistakenly added in one of previous commits
* Fix failing tests from test suite DeliveryDelayTest

> 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
>            Assignee: Alex Rudyy
>              Labels: policy-type, queue, ring
>             Fix For: qpid-java-7.0
>
>         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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to