Bug 754990
Summary: | qpidd broker ring queue limit depth working differently with --default-queue-limit=0 vs. default | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> | ||||
Component: | qpid-cpp | Assignee: | Gordon Sim <gsim> | ||||
Status: | CLOSED ERRATA | QA Contact: | Leonid Zhaldybin <lzhaldyb> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | Development | CC: | esammons, gsim, iboverma, jross, lzhaldyb, mcressma | ||||
Target Milestone: | 2.3 | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | qpid-cpp-0.18-1 | Doc Type: | Bug Fix | ||||
Doc Text: |
Cause:
The ring policy enforcement logic did not take account of the case where no maximum size was specified, only a maximum count.
Consequence:
A maximum size of 0 (i.e. unspecified) would result in a message being needless removed.
Fix:
The logic was updated to correctly handle the case where the size is not limited but the count is.
Result:
The policy is correctly enforced (and the behaviour is the same regardless of the default-queue-limit set).
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-03-06 18:54:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Frantisek Reznicek
2011-11-18 13:53:17 UTC
Created attachment 534397 [details]
Testing client (low-level API)
Good catch! Further fix committed upstream as http://svn.apache.org/viewvc?rev=1203835&view=rev. Issue still pending on qpid-*-0.14*. This issue is still not fixed in the latest Messaging 2.2 build. Observed on RHEL5.8 and RHEL6.3 both i386 and x86_64. Packages used for testing: qpid-cpp-0.14-18.el6_3 qpid-cpp-0.14-18.el5 Tested on RHEL5.8 and RHEL6.3 (both i386 and x86_64). The ring queue behaviour is now consistent, setting default-queue-limit=0 does not change it. Packages used for testing: RHEL5.8 qpid-cpp-client-0.18-1.el5 qpid-cpp-client-devel-0.18-1.el5 qpid-cpp-client-devel-docs-0.18-1.el5 qpid-cpp-client-rdma-0.18-1.el5 qpid-cpp-client-ssl-0.18-1.el5 qpid-cpp-mrg-debuginfo-0.18-1.el5 qpid-cpp-server-0.18-1.el5 qpid-cpp-server-cluster-0.18-1.el5 qpid-cpp-server-devel-0.18-1.el5 qpid-cpp-server-rdma-0.18-1.el5 qpid-cpp-server-ssl-0.18-1.el5 qpid-cpp-server-store-0.18-1.el5 qpid-cpp-server-xml-0.18-1.el5 RHEL6.3 qpid-cpp-client-0.18-1.el6_3 qpid-cpp-client-devel-0.18-1.el6_3 qpid-cpp-client-devel-docs-0.18-1.el6_3 qpid-cpp-client-rdma-0.18-1.el6_3 qpid-cpp-client-ssl-0.18-1.el6_3 qpid-cpp-debuginfo-0.18-1.el6_3 qpid-cpp-server-0.18-1.el6_3 qpid-cpp-server-cluster-0.18-1.el6_3 qpid-cpp-server-devel-0.18-1.el6_3 qpid-cpp-server-rdma-0.18-1.el6_3 qpid-cpp-server-ssl-0.18-1.el6_3 qpid-cpp-server-store-0.18-1.el6_3 qpid-cpp-server-xml-0.18-1.el6_3 -> VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0561.html |