Bug 1090368
Summary: | [Selectors] does not recognize redelivered message with amqp.redelivered | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Zdenek Kraus <zkraus> |
Component: | qpid-cpp | Assignee: | Andrew Stitcher <astitcher> |
Status: | CLOSED ERRATA | QA Contact: | Zdenek Kraus <zkraus> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | astitcher, iboverma, jross, lzhaldyb, mtoth |
Target Milestone: | 3.0 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qpid-cpp-0.22-40 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-24 15:11:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 453539 |
Description
Zdenek Kraus
2014-04-23 07:52:53 UTC
The 3.0 selector functionality should include the redelivered flag In my quick tests I am seeing a strange behaviour: The first time the message is redelivered it still matches the selector "amqp.redelivered=false" (although it has the Redelivered header) but subsequently it matches "amqp.redelivered=true" It may be that the header is set *after* the selector is run so that the selector test happens before the msg field is updated to take account of the redelivery. This is now fixed on the trunk branch of qpid in r1591183 [ https://svn.apache.org/r1591183 ] tested on RHEL 6.5 i686 && x86_64 with following packages: python-qpid-0.22-14.el6 qpid-proton-c-0.7-1.el6 qpid-cpp-server-devel-0.22-40.el6 qpid-cpp-server-ha-0.22-40.el6 qpid-jca-0.22-2.el6 qpid-cpp-server-0.22-40.el6 qpid-tools-0.22-12.el6 qpid-java-client-0.22-6.el6 qpid-qmf-debuginfo-0.22-31.el6 qpid-snmpd-debuginfo-1.0.0-16.el6 qpid-cpp-client-devel-docs-0.22-40.el6 qpid-cpp-client-0.22-40.el6 qpid-cpp-client-devel-0.22-40.el6 qpid-tests-0.22-15.el6 qpid-snmpd-1.0.0-16.el6 qpid-cpp-server-linearstore-0.22-40.el6 qpid-java-common-0.22-6.el6 qpid-java-example-0.22-6.el6 qpid-proton-debuginfo-0.7-1.el6 qpid-proton-c-devel-0.7-1.el6 python-qpid-qmf-0.22-31.el6 qpid-qmf-devel-0.22-31.el6 qpid-cpp-server-rdma-0.22-40.el6 qpid-cpp-server-xml-0.22-40.el6 qpid-jca-xarecovery-0.22-2.el6 perl-qpid-debuginfo-0.22-12.el6 qpid-qmf-0.22-31.el6 perl-qpid-0.22-12.el6 qpid-cpp-debuginfo-0.22-40.el6 qpid-cpp-client-rdma-0.22-40.el6 ruby-qpid-qmf-0.22-31.el6 works as expected. 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/RHEA-2014-1296.html |